Repository navigation
Allow CORS preflight with only origins configured - #423
Merged
Merged
Conversation
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.
Closes #383.
Default
cors_allowed_methodsto["*"]so JSON POST preflights succeed with only allowed origins configured in FastAPI and Litestar. Keep the header default at[]and document both defaults.Breaking changes
Applications that configure allowed origins and omit
cors_allowed_methodsnow allow all standard HTTP methods through CORS preflight. Set an explicit list to restrict methods. The 2.x migration guide documents the change.Verification
just lint-ci,just test-ci(635 tests, 100% coverage), andjust docs-buildpassed.