#30426: Make security headers default. -------------------------------------+------------------------------------- Reporter: Adam (Chainz) | Owner: Adam Johnson | (Chainz) Johnson Type: New feature | Status: assigned Component: Core (Other) | Version: master Severity: Normal | Resolution: Keywords: | Triage Stage: Accepted Has patch: 1 | Needs documentation: 1 Needs tests: 0 | Patch needs improvement: 1 Easy pickings: 0 | UI/UX: 0 -------------------------------------+-------------------------------------
Comment (by Florian Apolloner): Sure and I am fully in favor of making them a global default, I am just not sure if we can argue it given our policies… So if you all think that we should do it, I am +1 (with a rather prominent note in the release notes). That said I think only the `X_FRAME_OPTIONS` change would be relevant at all because I cannot imagine how one would rely on the behavior of the others to do something useful :) -- Ticket URL: <https://code.djangoproject.com/ticket/30426#comment:14> 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.70708c6614a00f906b68007fa32908bf%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.