-
Notifications
You must be signed in to change notification settings - Fork 11
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
Whitelist / Blacklist headers #5
Comments
From: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers
|
antoinechalifour
added a commit
that referenced
this issue
Aug 15, 2019
antoinechalifour
added a commit
that referenced
this issue
Aug 15, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now almost all headers are copied
... which is not that great (some are redundant, some do not make sense, some crash the app, list
host
...).Some headers have a "special role" and should not be forwarded as such :
We should investigate which header can be safely forwarded and which cannot :
Response headers
Cache-Control -> ✅
Content-Encoding -> ❌ (implies content decoding in memento)
Content-Security-Policy -> ✅
Content-Type -> ✅
Date -> ?
ETag -> ?
Expect-CT -> ?
Server -> ?
Set-Cookie -> ?
Strict-Transport-Security -> ?
Transfer-Encoding -> ❌
Vary -> ?
X-- -> ✅
Request headers
Accept -> ✅
Accept-Encoding -> ❌
Accept-Language -> ✅
Cache-Control -> ✅
Connection -> ?
Cookie -> ?
Host -> ?
If-None-Match -> ?
Referer -> ?
Upgrade-Insecure-Requests -> ?
User-Agent -> ✅
The text was updated successfully, but these errors were encountered: