Use Flask-CORS for more robust CORS configuration. #1121
Merged
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.
The API currently uses the
Access-Control-Allow-Origin
header, but notthe
Access-Control-Allow-Headers
header. This leads to CORS errorswhen using Safari, which sends the
Accept-Encoding
header with itsOPTIONS
requests. Rather than allowing theAccept-Encoding
header,this patch switches to Flask-CORS for CORS configuration, which has
better defaults and is easier to configure than settings CORS headers
manually.
Thanks @onezerojeremy and @noahmanger for help with debugging.
[Resolves https://github.com/fecgov/openFEC-web-app/issues/462]