On Mon, 24 Sep 2018 at 16:36, Willy Tarreau wrote:
>
> On Mon, Sep 24, 2018 at 02:30:35PM +, 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
> >
On Mon, Sep 24, 2018 at 02:30:35PM +, 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
> Hi Pierre,
Hi Willy,
> The close on the server side is expected, that's a limitation of the current
> design that we're addressing for 1.9 and which is much harder than initially
>expected. The reason is that streams are independent in H2 while in H1 the
> same stream remains idle and recycled
Hi Pierre,
On Mon, Sep 24, 2018 at 02:10:21PM +, Pierre Cheynier wrote:
> > You'll notice that in the HTTP/2 case, the stream is closed as you mentioned
> > (DATA len=0 + ES=1) then HAProxy immediately send FIN-ACK to the server.
> > Same for the client just after it forwarded the headers. It
> You'll notice that in the HTTP/2 case, the stream is closed as you mentioned
> (DATA len=0 + ES=1) then HAProxy immediately send FIN-ACK to the server.
> Same for the client just after it forwarded the headers. It never wait for
> any
> SSE frame.
EDIT: in fact, analyzing my capture, I see
Hi Lukas,
On Mon, Sep 24, 2018 at 01:46:57AM +0200, Lukas Tribus wrote:
> Hello,
>
>
> On Fri, 21 Sep 2018 at 15:45, Pierre Cheynier wrote:
> > Let me know if you see something obvious here, or if this is candidate to a
> > bug.
> >
> > We have a service using SSE through text/event-stream
Hello,
On Fri, 21 Sep 2018 at 15:45, Pierre Cheynier wrote:
> Let me know if you see something obvious here, or if this is candidate to a
> bug.
>
> We have a service using SSE through text/event-stream content-type.
>
> In HTTP/1.1 we have a normal stream as expected :
> < HTTP/1.1 200 OK
> <
Hi list,
We observed a weird behavior yesterday at introducing h2 in a preproduction
environment: *the connection is being closed by haproxy both on server and
client side by immediately sending a FIN/ACK when using SSE
(text/event-stream)*.
Let me know if you see something obvious here, or
8 matches
Mail list logo
