Skip to content
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

Disallow "hop-by-hop" headers in request_headers and response_headers #107

Open
chlily1 opened this issue Feb 14, 2019 · 0 comments
Open

Comments

@chlily1
Copy link

chlily1 commented Feb 14, 2019

Certain "hop-by-hop" headers (such as Proxy-Authenticate and Proxy-Authorization) are generally not visible to the destination server (e.g. they are stripped out by a proxy). Allowing origins to request their values via the request_headers and response_headers fields of a NEL report would violate the principle that NEL reports are meant to only contain information that would be available to the destination server.

Should there be a blacklist of headers whose values must not be sent in NEL reports? For example, RFC 2068 lists the following headers as "hop-by-hop":

  • Connection
  • Keep-Alive
  • Public
  • Proxy-Authenticate
  • Transfer-Encoding
  • Upgrade
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

1 participant