On Mon, 24 Sep 2018 at 16:36, Willy Tarreau <w...@1wt.eu> wrote: > > On Mon, Sep 24, 2018 at 02:30:35PM +0000, Pierre Cheynier wrote: > > OK, I conclude this SSE pattern is not working out-of-the-box when using h2 > > as of > > now. Is it still true even if setting the user set the proper connection > > headers on > > server side? > > Yes, it's irrelevant to the headers, it's related to the fact that each > request from an H2 connection is a different stream and that the server- > side idle connection is attached to a stream. So streams are short-lived > and the server-side connection is closed for now. But hopefully it won't > anymore for 1.9 ;-)
Just to be clear though; Content-Length or chunked transfer-encoding are required if you want to use keep-alive on the backend, even with HTTP/1.1 (or with other products). It's just that it won't work in H2 either way currently, but even if you just use HTTP/1.1 you'd need it. Lukas
