Remove auto_cors functionality #7
Merged
Conversation
This file contains 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
|
What issue are you having with your CORS implementation? |
|
The hardcoded response did not explicitly whitelist the PATCH method. |
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.
@nicotaing @rtjoseph11 @bgoldman @PikaDotus
Hey guys,
So I'm kind of torn on this. I just ran into an issue where this CORS implementation ran into some trouble, and on second thought, I'm not sure if this even belongs in Kenji in the first place. So instead of patching it to support PATCH; I figured I'd just remove it and recommend using Rack::Cors instead.
Thoughts?
-Kenneth