This change is a combination of 4 separate commits
to fix various bugs observed during android platform
testing.
https://android-review.googlesource.com/#/c/63781/
--------------------------------------------
Allow certificate inspections after connect.
We don't have to wait for the request to be sent
before allowing inspection of SSL certs. They can be
inspected as soon as the connection is established.
Fixes CTS test UrlConnectionTest#testInspectSslAfterConnect
https://android-review.googlesource.com/#/c/63821/
---------------------------------------------
Respect read timeout on recycled connections.
Partial fix for CTS test : URLConnectionTest#testGetKeepAlive.
https://android-review.googlesource.com/#/c/63782/
-----------------------------------
Fix HttpUrlConnection#isUsingProxy.
The earlier implementation disregarded what the
ProxySelector had to say. We now query the selected
route (if one has been established).
Fixes compatibility test:
HttpURLConnectionTest#testUsingProxySelector
https://android-review.googlesource.com/#/c/63872/
--------------------------------------------
Don't support anything other than Basic auth.
We should disregard authentication schemes other than
"Basic" and let clients handle them themselves.
The java Authenticator API gives us a user name and
password combination, but we can't know how to format
that information for any scheme other than basic.
Historically:
The JB implementation responds to challenges from an
arbitrary scheme "X" by sending a header with scheme
"X" but formatted like the "Basic" scheme.
The current implementation responds to challenges from
an arbitrary scheme "X" by sending a header with scheme
"Basic" and formatter like the "Basic scheme".
Partial fix for test cases in URLConnectionTest:
- testAuthenticateWithCommaSeparatedAuthenticationMethods
- testAuthenticateWithMultipleAuthenticationHeaders
Optional dependencies get included in the fat jar but are not transitive. Provided dependencies do NOT get included in the fat jar and are also not transitive.
I believe the former is a bug in the Maven assembly plugin so the latter case is used as a workaround.
Flags are not portable between SPDY/3 and HTTP/2.0,
so hide them in the reader & writer code.
Also rename SpdyReader to FrameReader and SpdyWriter to
FrameWriter. Other classes will be renamed as they become
independent of the underlying protocol.
This behavior-free refactoring makes the first baby steps towards
supporting HTTP/2.0. It adds indirection on the framing layer so
we can frame either using SPDY/3's syntax or HTTP/2.0's.
