[Webkit-unassigned] [Bug 220780] Null bytes aren't percent-encoded on urlencoded over POST

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sun Jan 24 08:55:53 PST 2021


https://bugs.webkit.org/show_bug.cgi?id=220780

--- Comment #6 from Andreu Botella <abb at randomunok.com> ---
(In reply to Alex Christensen from comment #5)
> We'll need more test coverage than that PR has.  Right now we use the
> encoding of the DOMFormData but other browsers seem to always use UTF-8.

The two "characters not in encoding..." tests set the form's accept-charset to windows-1252 and pass in all browsers. If Firefox and Chrome used UTF-8, they would instead fail with "a%C9%99b=c%EF%BF%BDd" and "%C3%A1=%F0%9F%92%A9".

But yeah, that PR was initially only meant to test newline normalizations on filenames in the urlencoded enctype, and since there were no other tests for urlencoded forms, I thought I'd add some corner cases as well. But in the time since we realized that that bug affected more than we initially thought. But feel free to comment on that PR to propose more test cases.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20210124/2432524d/attachment.htm>


More information about the webkit-unassigned mailing list