[5.6] hash_equals(): Expected user_string to be a string, null given #26132
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.
I am seeing random hash_equals(): Expected user_string to be a string, null given on my monitoring panel (see the log message at the end of this PR).
A user is probably messing with my app signed url, removing the value of the query parameter "signature".
Doing so, with the url
/foo/bar?signature=
, we getnull
for the result of$request->query('signature', '')
(https://github.com/illuminate/routing/blob/1e05259a8fa573413f8e12c3646a923d188f65c0/UrlGenerator.php#L354)To be sure to pass a string as the 2nd argument of the function hash_equals, I added a typecast before it.