This repository was archived by the owner on Feb 8, 2026. It is now read-only.
Open
Conversation
Member
|
Why not destroy? |
Author
|
I thought "destroy" and other fancy verbs are only for RESTful routes. |
Member
|
Sorry should be method DELETE. Like: |
Author
|
"DELETE /logout" request does not make much sense. Like "logout" is a resource and we're deleting it. Should I make all routing RESTful? Or just make this "DELETE /logout" thing? Be it POST or DELETE (which also will be simulated with a POST in browsers) does not matter in regard to CSRF. |
Contributor
|
@damianlegawiec @bbonislawski |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes #302
This is a breaking change since many users probably have overriden the view files, so I'm not sure this needs to be introduced to stable branches.