Le 7/22/23 à 21:48, Yaacov Akiba Slama a écrit :
Hi,
It seems that there is a bug in QUIC when using a fastcgi backend:
As soon as the size of the uploaded data is more than bufsize, the
server returns 400 Bad request and shows PH-- in the logs.
The problem occurs with both haproxy 2.8.1 and 2.9-dev2 (both build
quictls OpenSSL_1_1_1u-quic1).
When using h2 or an http backend, everything is ok.
Is it a known problem?
Hi,
Thanks for report. It is not a known issue, but I can confirm it. When H3
HEADERS frames are converted to the internal HTTP representation (HTX), a flag
is missing to specify a content-length was found.
I pushed a flag, it should be fixed:
commit e42241ed2b1df77beb1817eb9bcc46bab793f25c (HEAD -> master,
haproxy.org/master)
Author: Christopher Faulet <cfau...@haproxy.com>
Date: Mon Jul 24 11:37:10 2023 +0200
BUG/MEDIUM: h3: Properly report a C-L header was found to the HTX start-line
When H3 HEADERS frames are converted to HTX, if a Content-Length header was
found, the HTX start-line must be notified by setting HTX_SL_F_CLEN flag.
Some components may rely on this flag to know there is a content-length
without looping on headers to get the info.
Among other this, it is mandatory for the FCGI multiplexer because it must
announce the message body length.
This patch must be backported as far as 2.6.
--
Christopher Faulet
