I'm confused about the current state of server timeouts being exposed by
go1.17 for HTTP2 connections.
With a TLS/HTTP2 server that is streaming responses to a client that has
fetched and is in a readable stream loop, the stream stays up and the
server sends data whenever it wants - for exampl
https://github.com/golang/go/issues/49741
x/net/http2: http.Server.WriteTimeout does not fire if the http2 stream's
window is out of space. #49741
The 1.17 back port issue:
x/net/http2: http.Server.WriteTimeout does not fire if the http2 stream's
window is out of space. [1.17 backport] #49921
07 PM UTC-5 Ian Lance Taylor wrote:
> On Fri, Jan 28, 2022 at 6:44 AM frankre...@gmail.com
> wrote:
> >
> > https://github.com/golang/go/issues/49741
> >
> > x/net/http2: http.Server.WriteTimeout does not fire if the http2
> stream's window i
when I did, the timeout was honored. Without it, the
timeout on the http2 stream doesn't happen.
I've updated the issue #49741 although it is closed so I don't know if
anyone will see it.
On Saturday, January 29, 2022 at 10:52:56 AM UTC-5 frankre...@gmail.com
wrote:
> Sorr
