I have a Go 1.7.4 client which uses a custom HTTP transport to talk to my
Go 1.7.4 server. How do I ensure both client and server are properly
configured to use HTTP 2?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this
According to https://www.howsmyssl.com/s/api.html my Go 1.7.4 HTTPS client
does not support ticket-based TLS resumption.
How do I fix that?
Here is how I create the transport:
func NewTransport(caCert []byte, disableCompression, skipCertCheck bool)
*http.Transport {
caCertPool :=
Ping. I could not find any info on how to turn on TLS False Start support. Help.
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Say you have thousands of devices which you have control over. They all use
GPRS (2G), with ~700ms of latency. TLS handshake may cost ~4s sometimes when
mobile coverage is good and astonishing 20s when it is not or packet loss is
high by any reason.
False Start could make a huge difference.
AFAIK, big endian support for ARM is not available. Will it ever be
supported?
Out of curiosity, how hard is this task?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an
