Add QUERY route method support#60650
Closed
Afcyy wants to merge 2 commits into
Closed
Conversation
Member
|
Since you're updating a contract this would need to go to |
Author
|
Thanks, I'll retarget this to master. |
Author
|
I opened a new PR targeting |
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
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.
This PR adds first-class routing support for the HTTP
QUERYmethod.Laravel already supports custom methods through
Route::match()andRouter::addRoute(), but there is no nativeRoute::query()helper like there is forget,post,put,patch,delete, andoptions.With this change, applications can define
QUERYroutes directly:QUERY is also included in Route::any(), exposed through the route registrar and facade docs, and treated as a read request by PreventRequestForgery.
That last part is important because QUERY is defined as a safe HTTP method, so it should behave like GET, HEAD, and OPTIONS for CSRF purposes.
Tests cover direct router dispatching, route registrar usage, framework integration, cached routes, and CSRF middleware behavior.