Return explicit origin in CORS response when credentials are allowed#3137
Merged
Return explicit origin in CORS response when credentials are allowed#3137
Conversation
This was referenced Feb 14, 2026
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
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.
When
allow_origins=["*"]andallow_credentials=True, the simple response path now returns the explicit request origin instead of*. This aligns with the preflight path, which already does this since #1113.The previous approach inspected request headers (cookies) to decide when to echo the origin. This is unreliable - the server can't observe the client's
credentialsmode from request headers alone. Instead, we useallow_credentialsas the signal, same as django-cors-headers and envoy-proxy.Supersedes #1824, #2506, #3127, #3134.