feat: allow configuration of cors domains and credentials #159
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.
Description
Problem
For applications that use cookie-based auth, CORS domain wildcards are not allowed. Need to specify explicit domains instead. Plus,
Access-Control-Allow-Credentials
must be set totrue
.Solution
This makes CORS domains optionally configurable via
CORS_ALLOW_ORIGINS
, same forAccess-Control-Allow-Credentials
viaCORS_ALLOW_CREDENTIALS
. If no configuration is specified, current behavior is kept.