On Tue, May 25, 2021 at 11:09:22AM +0200, Tim Düsterhus, WoltLab GmbH wrote:
> Okay, here it is:
>
> https://github.com/haproxy/haproxy/issues/1266
Thank you!
Willy
Willy,
On 5/25/21 11:02 AM, Willy Tarreau wrote:
We've already noted that significant improvements in close/abort need to
be made to 1) process them better and 2) report them more accurately.
This is a tedious task which *will* inevitably cause regressions, but
it's the price to pay to improve
On Tue, May 25, 2021 at 10:30:27AM +0200, Tim Düsterhus, WoltLab GmbH wrote:
> > The 503 is just a byproduct of the aborted connection. That can sound
> > strange but what happens here is that the status was set after it was
> > noticed the processing ended without being able to connect to any
Willy,
On 5/21/21 6:48 PM, Willy Tarreau wrote:
I'd like your advice on a few log entries that confuse me. I am seeing HTTP
2.0 requests dying with a termination code of 'CC', i.e.:
C : the TCP session was unexpectedly aborted by the client.
C : the proxy was waiting for the
Hi Tim,
On Fri, May 21, 2021 at 10:22:15AM +0200, Tim Düsterhus, WoltLab GmbH wrote:
> Hi List
>
> [this email is not subscribed, please keep it in Cc]
>
> I'd like your advice on a few log entries that confuse me. I am seeing HTTP
> 2.0 requests dying with a termination code of 'CC', i.e.:
>
Hi List
[this email is not subscribed, please keep it in Cc]
I'd like your advice on a few log entries that confuse me. I am seeing
HTTP 2.0 requests dying with a termination code of 'CC', i.e.:
C : the TCP session was unexpectedly aborted by the client.
C : the proxy was
6 matches
Mail list logo
