Thanks. I logged https://github.com/golang/go/issues/18639.
On Thu, Jan 12, 2017 at 10:49 AM, James Bardin <j.bar...@gmail.com> wrote: > Form the SO link the frame was sent with ErrCode=NO_ERROR, which I would > assume would be handled silently by the transport. > > Not ruing out the ALBs doing something strange, but I would open an issue > none the less. > > > > > On Wednesday, January 11, 2017 at 5:18:54 PM UTC-5, Brian Fallik wrote: >> >> Hello Gophers, >> >> I'm trying to understand some behavior of Go's http client in >> http2-mode. Our code uses http.DefaultClient and on the server side we >> recently switched load balancers to a version that adds support for >> http/2. >> >> Go magically started using http/2 for us but now our clients >> occasionally observe GOAWAY frames sent from the load balancer. This >> manifests as a bug in the client since the error propagates up the >> stack. I've posted more details on SO: >> http://stackoverflow.com/questions/41592929/aws-alb-http-2-and-goaway >> >> I'm wondering if the http package expects users of the Client to >> explicitly handle GOAWAY frames or not? If so this seems like a worthy >> addition to the package docs since it's not obvious that the client >> behavior can change based on the server support for http/2. >> >> Thanks, >> brian > > -- > 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. -- 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.
