Adding support for OPTIONS requests to ESP8266WebServer #778
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
igrr
added a commit
that referenced
this pull request
Sep 18, 2015
Adding support for OPTIONS requests to ESP8266WebServer
igrr
added a commit
that referenced
this pull request
Oct 29, 2015
Adding support for OPTIONS requests to ESP8266WebServer
|
how do I enable cors in ESP8266WebServer? |
|
@alexiszecharies you are too lazy to give more info, so simple answer is "STFW". More sophisticated answer is "add custom response header 'Access-Control-Allow-Origin', '*'" os supersophisticated answer "use AsyncWebServer and add default header via .addHeader". |
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.
Needed CORS support, so adding OPTIONS as an HTTP verb.