headers: make sure to forward most target response headers #19
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit forwards all headers from the target server response, but
removes:
set-cookie
header to avoid transfering authentication data viathe proxy (it's not its role to authenticate any clients)
transfer-encoding
header, because it's a “hop-by-hop” headerand not supposed to be forwarded. The proxy reads the response (and
should thus consume the
transfer-encoding
header). If one day theproxy supports streaming responses, we will have to manually add this
header as per the HTTP spec.