Hi. Jun 1, 2020 1:37:55 PM Gaetan Deputier <[email protected]>:
> Hello! > > We have recently observed that a very small amount of our connections were > ended with the following state: CL--. Those connections are coming from > browsers and are correlated to weird behaviours observed in our downstream > application (where a HTTP header and a body seem to be exchanged with another > request). > > Looking at the documentation, this state that: > > C : the TCP session was unexpectedly aborted by the client. > L : the proxy was still transmitting LAST data to the client while the server > had already finished. This one is very rare as it can only happen when the > client dies while receiving the last packets. > > Does someone have more details about the L state specifically? What we should > we expect in our application in terms of sessions/packets/request? Please can you share the anonymized config and the output of `haproxy -vv` and `uname -a`. Regards Aleks > Thanks! > > G- >
