On Wed, Apr 13, 2022 at 10:36:00AM +0200, Amaury Denoyelle wrote: > On Tue, Apr 12, 2022 at 10:30:05AM -0600, Shawn Heisey wrote: > > On 4/12/22 09:45, Amaury Denoyelle wrote: > > > After much analysis of the code, it may be useful to have a run with the > > > stream traces as well : > > > $ trace stream sink buf0; trace stream level developer; trace stream > > > verbosity clean; trace stream start now > > All 3 traces enabled, this time it should only be for one connection, I > > think the last one there were two: > > https://paste.elyograg.org/view/a06556ef > > > You can also provide us your haproxy config file, just remove any > > > sensitive info if you have any. > > https://paste.elyograg.org/view/3f884d8f > > The acl lines with redacted info are not being matched for the connections > > that don't work, so it should have no connection to this problem. > I'm able to reproduce your issue with your config file. I can now > investigate the problem. I will let you know about any update, thanks.
Ok this seems related to 'option abortonclose'. Without this, I do not have a 400 error. Can you confirm me this behavior on your side please ? -- Amaury Denoyelle
