fix(security): reject wildcard origin with credentials in CORS middleware#2053
Merged
fix(security): reject wildcard origin with credentials in CORS middleware#2053
Conversation
…ware The CORS spec forbids Access-Control-Allow-Origin: * combined with Access-Control-Allow-Credentials: true. Browsers silently reject such responses, which often leads developers to weaken security further. The Cors middleware now throws Wheels.Cors.InvalidConfiguration at init() time when this invalid combination is detected. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.
Summary
Cors.cfcthat throwsWheels.Cors.InvalidConfigurationwhenallowOrigins="*"is combined withallowCredentials=trueCorsSpec.cfcverifying the validation and that valid configurations still workTest plan
🤖 Generated with Claude Code