Track URI status for the CORS bouncer #612
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
samholmes
force-pushed
the
sam/detecting-cors
branch
from
c02efc5
to
e15bd6e
Compare
swansontec
approved these changes
Aug 23, 2024
A host can and has returned different CORS headers per HTTP endpoint. Because of this, we cannot reliably assume that the entire hostname is either CORS-safe or not.
samholmes
force-pushed
the
sam/detecting-cors
branch
from
e15bd6e
to
d79e268
Compare
swansontec
approved these changes
Aug 23, 2024
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.
A host can and has returned different CORS headers per HTTP endpoint.
Because of this, we cannot reliably assume that the entire hostname is
either CORS-safe or not.
CHANGELOG
Does this branch warrant an entry to the CHANGELOG?
Dependencies
noneDescription
none