[Webkit-unassigned] [Bug 20559] decodeURLEscapeSequences will unescape NULLs and will mangle not encodable characters

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Aug 29 07:58:54 PDT 2008


------- Comment #8 from marv.decker at gmail.com  2008-08-29 07:58 PDT -------
(In reply to comment #7)
> Another thought is that if we have a code path that has a problem with URLs
> with null characters, it can possibly be triggered by making a URL with
> JavaScript's String.fromCharCode(0).

I believe that will get escaped by KURL automatically.

Sorry, I forgot to add the effect for the encoding problem:

I have part of a layout test that demonstrates the path being messed up. If you
have a page at "foo.com/asdf%F0" and you say document.location.pathname, it
will give you "/asdf\xFFFD" (the %F0 being replaced by the Unicode "replacement
character"). Although I don't know of any sites that break because of this,
it's hard to argue that it's not wrong.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the webkit-unassigned mailing list