#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 Ran Benita):
From a recent [https://adamj.eu/tech/2019/08/02/feature-policy-updates-
now-required-for-a-plus/ blog post] by Adam, and the
[https://scotthelme.co.uk/security-headers-updates/#removing-the-x-xss-
protection-header linked blog] and further links down it sounds like the
`X-Xss-Protection` header is deprecated or removed in modern browsers, and
maybe even [https://bugs.chromium.org/p/chromium/issues/detail?id=968591
harmful]. So maybe this one should not be enabled by default, and maybe
even the `security.W007` check should be removed?
--
Ticket URL: <https://code.djangoproject.com/ticket/30426#comment:15>
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.44d54ed9b3c368502548027d73647b04%40djangoproject.com.
