Bug 138957

Summary: encodeWithURLEscapeSequences doesn't encode several chars
Product: WebKit Reporter: cand <cand>
Component: PlatformAssignee: Nobody <webkit-unassigned>
Status: NEW ---    
Severity: Normal CC: ap
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: All   
OS: All   

Description cand 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.
Comment 1 Alexey Proskuryakov 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.