Skip to content

Remove XSS-Protection header from Nginx configs #9188

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nickvergessen merged 4 commits into from
Jul 1, 2025
Merged

Remove XSS-Protection header from Nginx configs #9188

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
669ebf6
Disable XSS-Protection Header
minecrawler Sep 29, 2022
934e5d2
docs(admin): remove X-XSS-Protection header from hardening section
MichaIng Jun 28, 2025
74dbee7
docs(admin): add critical changes for Nextcloud 32
MichaIng Jun 30, 2025
7f87872
docs(admin): grammar/wording
MichaIng Jun 30, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
docs(admin): grammar/wording 
Co-authored-by: Joas Schilling <[email protected]>
Signed-off-by: MichaIng <[email protected]>
  • Loading branch information
@MichaIng @nickvergessen
MichaIng and nickvergessen authored Jun 30, 2025
commit 7f8787206064dd22f693a8a9fe99119be731d347
2 changes: 1 addition & 1 deletion admin_manual/release_notes/upgrade_to_32.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,5 +12,5 @@ Web server configuration
------------------------

* Setup checks do not check for the ``X-XSS-Protection`` response header anymore. It has been removed from Nextcloud's ``.htaccess`` and you may want to adjust your webserver config to not serve it anymore.
XSS filtering was supported only until Chromium 78 and similarly old browsers, but had been found to cause more issues, including attack vectors, than it solves.
XSS filtering was supported only until Chromium 78 and similarly old browsers, but had been found to cause more issues, including attack vectors, than it solved.
Nowadays, aside of not serving the header at all, the only generally recommended value is ``0``. More context can be found in the `OWASP Cheat Sheet Series <https://cheatsheetseries.owasp.org/cheatsheets/HTTP_Headers_Cheat_Sheet.html#x-xss-protection>`_.