Accept scheme://host entries in TrustedOrigins - #211
Open
AshSgDe29071999 wants to merge 1 commit into
Open
Conversation
TrustedOrigins only compared against url.Host, so an entry like https://ui.example.com never matched. Host-only entries still work; full origins now match as well. See gorilla#192
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #192
TrustedOriginscompared onlyurl.Host, so an entry likehttps://ui.example.comnever matched Origin/Referer checks. README examples use a bare host, but callers who passed a full Origin (including scheme) were rejected after 1.7.3.Host-only entries still match. Full origins of the form
scheme://host[:port]now match as well.