-
Notifications
You must be signed in to change notification settings - Fork 8k
Fix GH-20366 ext/uri: Do not throw ValueError on null-byte #20489
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
Fix GH-20366 ext/uri: Do not throw ValueError on null-byte #20489
Conversation
|
Is this for master or 8.5? And can it wait for 8.5.1? |
Sorry! As always: I didn't set the target... It's a bug fix which fixes null-byte handling for WHATWG. It is completely broken in the RC-s right now. I think it's not a deal-breaker for 8.5.0... It seems like an edge case for me. @DanielEScherzer |
ndossche
left a comment
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 think this is right
TimWolla
left a comment
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.
LGTM, but I would prefer the hexadecimal \x00 instead of the octal \0 in tests, because the latter can accidentally capture additional characters afterwards if they happen to be numeric.
|
Okay, this isn't in 8.5.0, to RM objections to the bug fix for 8.5.1 |
5b94e0c to
139983f
Compare
I can workaround this in a followup test improvement. |
Fixes #20366
We still need to verify if ext/uri can handle null bytes properly.