Allow cors when in extened mode#48
Open
fishrockz wants to merge 1 commit into
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hi
This is a great tool, thank you very much!
I was using it with https://github.com/emilk/ehttp see demo: https://emilk.github.io/ehttp/index.html
And when i pointed the demo at anything from this server i got cross site protection errors.
The rust axum eco system seems quite cool so i was able to quickly add cros headers in the extended mode.
I find cors checks to normally be in the way when im developing but it can also be good to have your dev tools mimic what your prod will look like. a lot of sights do allow cors for some pages so im not sure if this should be on or off.
Feel free to close this if its not helpful but as i had it working i thought i should share.