-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[HttpFoundation] Add support for parsing non-POST requests using request_parse_body() (PHP 8.4) #59358
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
rottifant
wants to merge
4
commits into
symfony:7.3
Choose a base branch
from
rottifant:7.3
base: 7.3
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
[HttpFoundation] Add support for parsing non-POST requests using request_parse_body() (PHP 8.4) #59358
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
960f619
[HttpFoundation] Add support for `request_parse_body` in Request::cre…
rottifant b6ebc60
[HttpFoundation] Usage of PHP_VERSION_ID
rottifant 699e21e
[HttpFoundation] CS Patch, no overwriting of globals
rottifant 2be5ac2
Merge branch 'symfony:7.3' into 7.3
rottifant File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd let this check on the content-type to the request_parse_body function, no need to implement it ourselves
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you mean?
A content type check is required because if, for example, a request with content-type
application/json
is passed to the function, it will throwRequestParseBodyException: Content-Type "application/json" is not supported
. Or are we going to catch and handle it?RequestParseBodyException
is also thrown with invalid content, not just unsupported.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean the check for the content-type: we can catch the exception and deal with it instead of checking the content-type ourselves (and diverging from the native check).
We have to add logic to deal with the exception anyway, we cannot let it bubble down unhandled (createFromGlobals isn't expected to throw such exceptions).
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, my bad. I overlooked the "on the content-type" in your message...
I checked this because
RequestParseBodyException
is also thrown with invalid content, not just unsupported Content-Type. Or are we going to differentiate this?