Updated README.md to add a section "CORS on Flutter Web" #1763
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.
CORS on Flutter Web
When using Dio with Flutter Web, be aware of Web Browser CORS Pre-flight Requests. You won't encounter this on mobile platforms like Android/IOS. However, Pre-flight requests always happen with Flutter web when one makes a REST Api call such as dio.post() or dio.get() with headers.
The way to handle browser pre-flight requests is to enable CORS on your web server. Most web server frameworks or libraries provide CORS middleware to handle browser pre-flight requests.
New Pull Request Checklist
main
branch to avoid conflicts (via merge from master or rebase)CHANGELOG.md
in the corresponding packageAdditional context and info (if any)