#30426: Make security headers default
-------------------------------------+-------------------------------------
Reporter: Adam (Chainz) | Owner: Adam
Johnson | (Chainz) Johnson
Type: New feature | Status: assigned
Component: Core (Other) | Version: 2.2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Adam (Chainz) Johnson):
I don't think there are many downsides to changing the template. We
already ask developers to learn about these flags before production in
`manage.py check --deploy`, so having them visible and on by default
pushes this earlier in development and reduces the risk of writing
incompatible, less secure code to begin with, on new projects.
Changing the defaults via the deprecation timeline risks breaking sites
(sometimes subtly) for each of these headers, since they disable some
(bad) browser behaviour. We can probably force users to explicitly set the
flags in their settings file in the version before the default is
switched. I think there's a precedent but can't remember which setting.
--
Ticket URL: <https://code.djangoproject.com/ticket/30426#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.4c8afcc1b3ad0e255d78c5ad0d758981%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
