Thanks Valentine for all that precious information. I'll need some time and will probably start trying all the 2.9 versions to maybe identify the one that brought this conflict.
This is running in Docker and I only tested with the '2.9' tag, so it will be interesting to bisect the 2.9 releases first. Cheers,- Patrick - On Tue, Sep 24, 2024 at 6:39 PM Valentine Krasnobaeva < vkrasnoba...@haproxy.com> wrote: > Hi Patrick ! > > Thanks for reporting this ! > > 1. To have more detailed logs you could enable traces on stderr by > starting haproxy like this: > > ./haproxy -f haproxy.cfg -dt h1:developer:complete,h2:developer:complete > > See more details about this option below. Basically, with developer > level it will give you very detailed log. > > https://docs.haproxy.org/2.9/management.html#3 > > 2. tcpdumps from kibana side, haproxy node and elastic node will be > usefull (one backend configuration use case). > > 3. we also need to have a look at you configuration. > > There are some bugfixes for http, which we backported in 2.9 and 2.8. > > We maintain full Changelog lists for each version, but even if you > filter commit titles from these lists with http, there will be a lot: > > http://git.haproxy.org/?p=haproxy-2.8.git;a=blob_plain;f=CHANGELOG > > http://git.haproxy.org/?p=haproxy-2.9.git;a=blob_plain;f=CHANGELOG > > > So, you configuration (enabled http features and its combinations, etc) > + tcpdumps + traces output will help to point to some commits in 2.9, > which introduced such behaviour. > > > Also, just to precise, you've downgraded first untill 2.9.11 ? > > -- > > Bien cordialement, > Valentine > >
