Change flask_cors to be applied after blue print is initalized #286
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
alesanchezr
approved these changes
Nov 9, 2023
AngelDPL
pushed a commit
to 4GeeksAcademy/Spain-94-Flow
that referenced
this pull request
Apr 5, 2025
…to_routes Change flask_cors to be applied after blue print is initalized
kachaparth
pushed a commit
to kachaparth/react-flask-hello
that referenced
this pull request
May 20, 2025
…to_routes Change flask_cors to be applied after blue print is initalized
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.
According to the documentation for
flask_cors, we apply CORS after applying blue_print, not in the app directly. This PR is trying to solve the CORS problem that sometimes appears.Docs : https://flask-cors.readthedocs.io/en/latest/api.html#using-cors-with-blueprints