| Age | Commit message (Collapse) | Author |
|---|
|
This is a "How was this ever working?" update.
1. As it turns out, when you customize a Transport for an
http.Client, the transport is 'naturally' an HTTP1 transport.
To make it connect via HTTP2, you must use an http2.Transport
from the golang.org/x/net/http2 package.
2. Add support for logging TLS per-session keys in order
to aid debugging.
|
|
|
|
By default go's network stack "helpfully" reuses the Transports
among http.Clients. This will artifically inhibit the full use
of the network. Creating new Transports for every http.Client
will keep this from happening.
|
|
|
|
Try intercepting a reader.
|
|
The previous method for reading the download was slow -- it
involved too many "context switches" out of library code where
the reading was actually happening. This method appears to be
better. We'll see.
|
|
Improve robustness of the client in the case(s) where a network
goes away in the middle of the test. Report errors properly in
these cases and gracefully end the test.
|
|
|
|
|
