On 25/07/2023 12:04, Christopher Faulet wrote:
With more intensive tests, I'm able to reproduce it time to time. It is timing dependent. It happens when the last 2 DATA frames are decodes in same time. The end of the request is detected to early, on the first DATA frame instead of the last one. I must validate my fix with Amaury but it should be fixed soon.
I just tested again using curl 8.2.1 and it seems that my problem was caused by a bug in curl 8.1.2 ( https://github.com/curl/curl/issues/11389 ) which was already fixed by the https://github.com/curl/curl/pull/11390
So the original bug was indeed fixed by your commit (e42241ed2b1df77beb1817eb9bcc46bab793f25c). BTW, I tested also on top of the current haproxy-2.8/master and everything works.
Thanks a lot for your help! --yas
