Opened 7 years ago

Closed 7 years ago

Last modified 5 years ago

#27829 closed Cleanup/optimization (fixed)

Deprecate DEFAULT_CONTENT_TYPE setting

Reported by: Adam Johnson Owned by: nobody
Component: HTTP handling Version: 1.11
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

After a ​mailing list discussion there was consensus that the DEFAULT_CONTENT_TYPE setting is no longer useful since HTML5 has overtaken XHTML and that it could be deprecated.

For reference, the setting has lead to a number of bug reports such as the one that kicked off the discussion, #23908, and others such as #24598, #20822, #11683, #5704, etc.

Change History (5)

comment:1 by Tim Graham, 7 years ago

Summary: Deprecate DEFAULT_CONTENT_TYPE → Deprecate DEFAULT_CONTENT_TYPE setting
Triage Stage: Unreviewed → Accepted

comment:2 by Tim Graham, 7 years ago

Has patch: set

​PR

comment:3 by GitHub <noreply@…>, 7 years ago

Resolution: → fixed
Status: new → closed

In 80493b08:

Fixed #27829 -- Deprecated settings.DEFAULT_CONTENT_TYPE.

comment:4 by Tim Graham <timograham@…>, 6 years ago

In 99d4fc18:

Refs #27829 -- Added warning for settings.DEFAULT_CONTENT_TYPE usage outside of Django.

comment:5 by Tim Graham <timograham@…>, 5 years ago

In 8045dff:

Refs #27829 -- Removed settings.DEFAULT_CONTENT_TYPE per deprecation timeline.

Note: See TracTickets for help on using tickets.
Back to Top