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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Aug 28 22:27:28 PDT 2008


------- Comment #6 from darin at apple.com  2008-08-28 22:27 PDT -------
(In reply to comment #5)
> I'm not arguing for or against this change, but Windows APIs do special-case
> NULLs, so routines that validate strings for using in Windows system calls
> often must understand the magical, string-terminating semantics of NULL.

Makes sense. Any code path that involves calling
String::charactersWithNullTermination could run afoul of a null character, and
although I can't find any examples of doing that with a URL or a piece of a URL
it's possible there could be some.

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