Remove hop-by-hop headers from forward auth response #3900
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
juliens
added
status/2-needs-review
kind/bug/fix
|
Thanks all of you for this really fast merge... |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
Hop-By-Hop headers from a ForwardAuth response get removed.
Motivation
Hop-By-Hop headers from a ForwardAuth response (e.g. Redirect) should never be passed to the receiver. Failing to do so results in problems with Safari, which shows a "NSPOSIXErrorDomain:100" error if a ForwardAuth on a HTTP-1.1 server sends a redirect.
Fixes #3039
More