feat: optional CORS #92
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
vipulchhabra99
force-pushed
the
CORS_seperate
branch
2 times, most recently
from
746f85f to
8c93196
Compare
vipulchhabra99
force-pushed
the
CORS_seperate
branch
from
8c93196 to
2cd76ca
Compare
uniqueg
changed the title
vipulchhabra99
force-pushed
the
CORS_seperate
branch
from
7b68fda to
86b418d
Compare
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.
corsto the SecurityConfig that takes an object of the new modelCORSConfigCORSConfigcurrently has a single propertyenablethat takes abooland defaults toTrueCORSConfigis open for extension in case other behavior will be implemented in the future (e.g., resource- or route-specific CORS)Fixes #90