Fix handling of escaped slashes ("%2f") in FTP paths.

Chrome was unescaping them before sending requests to the server, which
would map "ftp://foo/bar%2f..%2fblah" to requesting path "/bar/../blah"
from the FTP server, which is weird.  It now requests the file named
"bar%2f..%2fblah" instead.  Worth noting that GURL considers this to be
a separate url from ftp://foo/blah, so its best to be consistent with
that behavior.  Also, when Chrome sees an FTP file with %'s in its name,
it unescapes them, so Chrome would never generate a URL with "%2f" in
it, but they could still come from external sources.

This CL also fixes the title of directory listings of paths with "%2f"
in them - ftp://foo/bar%2f/baz will now say "Index of /bar%2f/" instead
of "Index of /bar//".

BUG=597056

Review URL: https://codereview.chromium.org/1827893002

Cr-Commit-Position: refs/heads/master@{#382961}

0 files changed, 0 insertions, 0 deletions