-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[WIP] Explicitly disallowing serialization of objects as controller attributes... #8263
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
Closed
Closed
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
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
Next
Next commit
Explicitly disallowing serialization of objects as controller attribu…
…tes in non-inline fragment renderers
- Loading branch information
commit bf8c2f8baea9ca6acccc0843c921e954d9dbc7a5
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
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
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.
Missing line break. Also, make a strict comparison
!==
.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.
The non-strict comparison is necessary, because http_build_query does mangle integer attributes into being strings. This comparison is basically just a quick smell-check for any non-trivial object data.
I think this prompts a higher-level discussion: why not actually use PHP serialize + base64 encode for encoding controller params? Unlike regular query-string where the int -> string conversion is expected, I think that in this case we can encode int/boolean/string/stdClass (but no other objects) using native serialize to fully preserve scalar typing and make actual controller developer not worry about accidentally stringified values. For serialize() data I'd recommend using base64 instead of directly piping into urlencode() because it's a true binary blob.
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.
For that matter, non-anonymous objects can then also be serialized as well - since the URLs are signed we don't need to worry too much about tampering