CSP: Document proposed solution to redirect-target path leakage. #18
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
In a nutshell, this proposal patches the matching algorithm to ignore the path component in source expressions if the URL being matched is the result of an HTTP redirect. Since these requests will now be host/scheme based, we still get reasonable protection by limiting resources to allowed origins after a redirect, while not allowing malicious parties to brute-force paths through cleverness.
mikewest
added a commit
that referenced
this pull request
May 21, 2014
CSP: Document proposed solution to redirect-target path leakage.
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.
In a nutshell, this proposal patches the matching algorithm to ignore
the path component in source expressions if the URL being matched is the
result of an HTTP redirect. Since these requests will now be host/scheme
based, we still get reasonable protection by limiting resources to
allowed origins after a redirect, while not allowing malicious parties
to brute-force paths through cleverness.