Fix for a runtime exception that could occur with bad redirects

If the redirect address contained an invalid % escape sequence
the request would fail with a runtime exception when the URI
object was created to be passed to ProxySelector. Now the
bad escape sequence is itself escaped. e.g. %0& -> %250&. The
actual request made is unchanged (i.e. it will still contain

This is related to changes in external/okhttp.

Bug: 27590872
(cherry picked from commit 7ac2143d73aa65c1d8bdb448ad11ee90a5503a85)

Change-Id: Ic2a5173edb817822c185694d7b64e9e3a2a56b91
1 file changed