Hi Willy,
> Yes definitely. There's no emergency but any extra info you can provide
> will help us of course.
I tested with HTTP/1.1 on the client side and HAProxy was flawless, so this is
very, very likely limited to h2.
> That could indeed. No need to have something very advanced, if you
On Tue, Mar 19, 2019 at 08:59:38AM -0400, Luke Seelenbinder wrote:
> Makes sense, Willy. Thanks for continuing to investigate this.
>
> > I'm assuming that this is always reproducible with H2 on the front and
> > H1 on the back.
>
> I have not tried it with H1 -> H1, but I assume that case works
Makes sense, Willy. Thanks for continuing to investigate this.
> I'm assuming that this is always reproducible with H2 on the front and
> H1 on the back.
I have not tried it with H1 -> H1, but I assume that case works correctly.
Would it be helpful if I proved it one way or the other?
> I'll
Hi Luke,
On Mon, Mar 18, 2019 at 11:14:12AM -0400, Luke Seelenbinder wrote:
(...)
> If I disable HTX, everything flows per normal and the status codes are even
> correctly -1.
>
> I've replicated this on 1.9.4, 1.9.x master, and 2.0-dev master branches. The
> global "this will work" and "this
Hi Willy,
Unfortunately, I spoke too soon in my last email. After hitting send, I went
down the rabbit hole again and uncovered some behaviors I thought we'd rooted
out. Namely, any time I use HTX mode with an H2 fe -> H1 or H2 backend and have
frequent request cancellation as discussed
Hi Willy,
I finally had the opportunity to try out `option abortonclose`.
Initially, it made the problem much worse. Instead of occasionally incorrect
status codes in the logs, I saw requests fail in the following manner:
[18/Mar/2019:12:30:08.040] stadiamaps~ tile/tile1 0/18603/-1/-1/24804
On Mon, Mar 04, 2019 at 11:45:53AM +, Luke Seelenbinder wrote:
> Hi Willy,
>
> > Do you have "option abortonclose" in your config ?
>
> We do not have abortonclose. Do you recommend this if we have a lot of
> client-side request aborts (but not connection level closes)? From reading
> the
Hi Willy,
> Do you have "option abortonclose" in your config ?
We do not have abortonclose. Do you recommend this if we have a lot of
client-side request aborts (but not connection level closes)? From reading the
docs, I came away conflicted as to the implications. :-)
Best,
Luke
—
Luke
Hi Luke,
On Fri, Feb 22, 2019 at 10:03:12AM +, Luke Seelenbinder wrote:
> Hi List, Willy,
>
> After transitioning to 1.9.4, I can say things are much more stable when
> using h2 on the frontend. Thanks for all the bug fixes and patches since
> 1.9.0! I'll be upgrading to 1.9.5 when it comes
Hi List, Willy,
After transitioning to 1.9.4, I can say things are much more stable when using
h2 on the frontend. Thanks for all the bug fixes and patches since 1.9.0! I'll
be upgrading to 1.9.5 when it comes out, so I'm looking forward to that.
I have one question: we track error rates
10 matches
Mail list logo
