Deprecate Web Browser XSS Protection Not Enabled? #5849
Closed
Comments
|
Yeah, I noticed that too. I'm good with deprecating it. |
|
Ref:
|
kingthorin
added a commit
to kingthorin/zaproxy
that referenced
this issue
Feb 7, 2020
Per zaproxy#5849 and zaproxy#5788 Signed-off-by: kingthorin <kingthorin@users.noreply.github.com>
Merged
kingthorin
added a commit
to kingthorin/zap-extensions
that referenced
this issue
Feb 7, 2020
Per zaproxy/zaproxy#5849 and zaproxy/zaproxy#5788 Signed-off-by: kingthorin <kingthorin@users.noreply.github.com>
kingthorin
added a commit
to kingthorin/zap-extensions
that referenced
this issue
Feb 7, 2020
Per zaproxy/zaproxy#5849 and zaproxy/zaproxy#5788 Signed-off-by: kingthorin <kingthorin@users.noreply.github.com>
kingthorin
added a commit
to kingthorin/zap-extensions
that referenced
this issue
Feb 7, 2020
Per zaproxy/zaproxy#5849 and zaproxy/zaproxy#5788 Signed-off-by: kingthorin <kingthorin@users.noreply.github.com>
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
See: https://security.stackexchange.com/questions/225415/are-favicon-ico-robots-text-sitemap-xml-vulnerable-to-xss
Per:
https://caniuse.com/#search=X-XSS-Protection
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-XSS-Protection
The text was updated successfully, but these errors were encountered: