[HttpFoundation] Deprecate HTTP method override for methods GET, HEAD, CONNECT and TRACE #61949
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
stof
reviewed
Oct 3, 2025
alexpott
reviewed
Oct 6, 2025
nicolas-grekas
force-pushed
the
deprec-x-method
branch
from
d740bd0 to
a2e3af9
Compare
fabpot
approved these changes
Oct 10, 2025
…, CONNECT and TRACE
fabpot
force-pushed
the
deprec-x-method
branch
from
a2e3af9 to
167edf1
Compare
|
Thank you @nicolas-grekas. |
This was referenced Oct 27, 2025
Merged
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Using HTTP method overriding (or HTTP verb tunneling) for those methods is dangerous and unneeded: the technique has been created to submit forms using HTTP verbs that browsers don't support. GET is not one of them, so that the trick shouldn't be applied to it. HEAD, CONNECT, TRACE are also NOT something browser should do - there's no point for a Symfony app to be the recipient of such requests (well, HEAD maybe, but since it should mimic a GET, it has to be in the list).
This should make Symfony safer by default, since using a POST to tunnel a GET might lead to security-sensitive stuff.