On 31/07/2018, 22:07, Simone Bordet wrote: ..
Finally, I would consider TLS handshake time as part of the request data: the cost will be paid by the first request and capped by "total" timeout (not connectTimeout). With TLS 1.3 optimizations, it may be just few TLS bytes before the encrypted request bytes. Thanks!
On this point, why not time the handshake as part of the connect timeout? Then you would have consistency for all response times regardless of whether a new TLS connection is being set up, or an existing one reused. Granted TLS 1.3 improves this, but there is still overhead, and significantly more for new TLS sessions pre 1.3.
Michael.
