We tried:
if len(os.Getenv("DISABLE_HTTP2")) > 0 {
http.DefaultClient.Transport = &http.Transport{
TLSNextProto: make(map[string]func(string, *tls.Conn)
http.RoundTripper),
}
}
But the effect was the same as with GODEBUG=http2client=0, just an EOF.
Will keep trying.
If it is relevant we're using "golang.org/x/crypto/acme/autocert" for TLS
and our service is only reachable through HTTPS. The certificate is valid
and working and will not expire soon.
On Friday, July 14, 2017 at 11:10:39 AM UTC+2, thwd wrote:
>
> We use GKE (Kubernetes on GCE) and have Go HTTP/2 pods running there. In
> front of them is a service of type "LoadBalancer". As I understand, these
> are nginx instances.
>
> Since this week, the error described in issue 17066 [1] is happening about
> 90% of the time when we connect a client via HTTP/2 (it works sporadically).
>
> This project has been running for over a year with no issues until this
> week. I suspect Google deployed an update or such to the load balancers.
>
> We've tried setting GODEBUG=http2client=0 (as described in package
> net/http doc) to use HTTP 1.1 but all we get is a io.EOF error on
> http.DefaultClient.Do.
>
> I'm working on a workaround, will post how we solve it. Any ideas or
> suggestions are welcome.
>
> [1] https://github.com/golang/go/issues/17066
>
--
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 golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
