redirect with 303 so as not to carry :DELETE method #1
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
pat
added a commit
that referenced
this pull request
Jun 8, 2014
redirect with 303 so as not to carry :DELETE method
|
I think something's been added to the HTTP spec just in the last few days about this - but yeah, 303 sounds like the smart approach here. |
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.
The 302 redirect causes the HTML method to be preserved and carried across. So when redirecting from the index, when unliking it will push the user back to the destroy action.
Added 303 to redirect to prevent the method sticking.
I know all of this is customisable, it's just not the best default behaviour. Results in deleting objects when unliking.