Skip to content

Allowing various anti-spoofing headers for outgoing requests #2

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.

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

Open
lucacasonato opened this issue Feb 7, 2025 · 1 comment
Open

Comments

@lucacasonato
Copy link
Member

In the browser, accept-charset, date, dnt, origin, referer, via, proxy-*, sec-*, x-http-method, x-http-method-override, and x-method-override are disallowed because they should not be spoofable by users.

On the server however, these are not security sensitive, so they do not have to be stripped from outgoing requests.

@andreubotella
Copy link
Member

Access-Control-Request-Headers and Access-Control-Request-Method are also CORS-related headers which shouldn't be stripped on the server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants