Django's docs says, "Modern browsers don’t honor X-XSS-Protection HTTP
header anymore. Although the setting offers little practical benefit, you
may still want to set the header if you support older browsers."
https://docs.djangoproject.com/en/3.2/ref/settings/#secure-browser-xss-
filter
According to Mozilla's docs, the header is supported by IE8 and Safari.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-XSS-Protection
In Django 3.0, the system check that suggested using this setting was
removed (#30680).
--
Ticket URL: <https://code.djangoproject.com/ticket/32678>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* has_patch: 0 => 1
Comment:
[https://github.com/django/django/pull/14306 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/32678#comment:1>
* keywords: => security, xss
* easy: 0 => 1
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/32678#comment:2>
* stage: Accepted => Ready for checkin
--
Ticket URL: <https://code.djangoproject.com/ticket/32678#comment:3>
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"54da6e2ac20bde80e0de9e35aa0c40ae1dd13943" 54da6e2]:
{{{
#!CommitTicketReference repository=""
revision="54da6e2ac20bde80e0de9e35aa0c40ae1dd13943"
Fixed #32678 -- Removed SECURE_BROWSER_XSS_FILTER setting.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32678#comment:4>