NEW 138957
encodeWithURLEscapeSequences doesn't encode several chars
https://bugs.webkit.org/show_bug.cgi?id=138957
Summary encodeWithURLEscapeSequences doesn't encode several chars
cand
Reported 2014-11-21 03:23:59 PST
encodeWithURLEscapeSequences should URL-encode all needed chars. Currently it doesn't encode ?, #, +, & at least, all of which cause trouble. For example, try encoding the string "c++ vector". It becomes "c+++vector", which when sent to a page obviously becomes "c vector", not what the user intended.
Attachments
Alexey Proskuryakov
Comment 1 2014-11-21 16:17:41 PST
I briefly looked into this in the past, and I think that the situation is substantially more complicated. Different parts of a URL need different escaping, so we need a more involved change than just adding more characters to this function.
Note You need to log in before you can comment on or make changes to this bug.