I am chasing an issue where an upgrade from a very old version of haproxy broke some of our tests. By trial and error, I have reduced the problem down to the length of the header field name going over 256 bytes.
the log line is
2023-10-16 22:36:32.229412 ch1-fb2 haproxy[3434507]: ::ffff:10.80.40.178:49734 [16/Oct/2023:22:36:32.228] haproxy-frontend~ haproxy-frontend/ -1/-1/-1/-1/0 400 0 - - PR-- 3/1/0/0/0 0/0 “”
and the captured error message is
ir@ch1-fb2:/opt/ir/haproxy$ sudo socat - UNIX-CONNECT:/run/haproxy/admin.sock
show errors
Total events captured on [16/Oct/2023:22:38:41.935] : 5
[16/Oct/2023:22:36:32.228] frontend haproxy-frontend (#2): invalid request
backend (#-1), server (#-1), event #4, src ::ffff:10.80.40.178:49734
buffer starts at 0 (including 0 out), 29940 free,
len 2828, wraps at 32720, error at position 2828
H1 connection flags 0x00000100, H1 stream flags 0x00000890
H1 msg state MSG_DATA(27), H1 msg flags 0x00001511
H1 chunk len 0 bytes, H1 body len 0 bytes :
00000 PUT /metadata-test-bkt/object_name HTTP/1.1\r\n
00045 Host: 10.89.50.68\r\n
00064 Accept-Encoding: identity\r\n
00091 x-amz-meta-12345678901234561234567890123456123456789012345612345678901
00161+ 2345612345678901234561234567890123456123456789012345612345678901234561
00231+ 2345678901234561234567890123456123456789012345612345678901234561234567
00301+ 890123456123456789012345612345678901234561234567890123456: 12345678901
00371+ 2345612345678901234561234567890123456123456789012345612345678901234561
00441+ 2345678901234561234567890123456123456789012345612345678901234561234567
00511+ 8901234561234567890123456123456789012345612345678901234561234567890123
00581+ 4561234567890123456123456789012345612345678901234561234567890123456123
00651+ 4567890123456123456789012345612345678901234561234567890123456123456789
00721+ 0123456123456789012345612345678901234561234567890123456123456789012345
00791+ 6123456789012345612345678901234561234567890123456123456789012345612345
00861+ 6789012345612345678901234561234567890123456123456789012345612345678901
00931+ 2345612345678901234561234567890123456123456789012345612345678901234561
01001+ 2345678901234561234567890123456123456789012345612345678901234561234567
01071+ 8901234561234567890123456123456789012345612345678901234561234567890123
01141+ 4561234567890123456123456789012345612345678901234561234567890123456123
01211+ 4567890123456123456789012345612345678901234561234567890123456123456789
01281+ 0123456123456789012345612345678901234561234567890123456123456789012345
01351+ 6123456789012345612345678901234561234567890123456123456789012345612345
01421+ 6789012345612345678901234561234567890123456123456789012345612345678901
01491+ 2345612345678901234561234567890123456123456789012345612345678901234561
01561+ 2345678901234561234567890123456123456789012345612345678901234561234567
01631+ 8901234561234567890123456123456789012345612345678901234561234567890123
01701+ 4561234567890123456123456789012345612345678901234561234567890123456123
01771+ 4567890123456123456789012345612345678901234561234567890123456123456789
01841+ 0123456123456789012345612345678901234561234567890123456\r\n
01898 User-Agent: Boto3/1.28.64 md/Botocore#1.31.64 ua/2.0 os/linux#5.15.0-2
01968+ 5-generic md/arch#x86_64 lang/python#3.10.6 md/pyimpl#CPython cfg/retr
02038+ y-mode#legacy Botocore/1.31.64 Resource\r\n
02079 Content-MD5: 1B2M2Y8AsgTpgAmY7PhCfg==\r\n
02118 X-Amz-Date: 20231016T223604Z\r\n
02148 X-Amz-Content-SHA256: UNSIGNED-PAYLOAD\r\n
02188 Authorization: AWS4-HMAC-SHA256 Credential=PSFBSAZRNMOMKDJGLBDNDBIIOFF
02258+ OOLMGELBFBKINIO/20231016/us-east-1/s3/aws4_request, SignedHeaders=cont
02328+ ent-md5;host;x-amz-content-sha256;x-amz-date;x-amz-meta-12345678901234
02398+ 5612345678901234561234567890123456123456789012345612345678901234561234
02468+ 5678901234561234567890123456123456789012345612345678901234561234567890
02538+ 1234561234567890123456123456789012345612345678901234561234567890123456
02608+ 12345678901234561234567890123456, Signature=d6558bdb795bb25a8537874de9
02678+ 9603c22a56f6fd56f96b40672cbb404a79dd47\r\n
02718 amz-sdk-invocation-id: 8c6dca1c-07cb-4c1b-8d57-906766787130\r\n
02779 amz-sdk-request: attempt=1\r\n
02807 Content-Length: 0\r\n
02826 \r\n
If I shrink the field name for the query by 16 bytes, haproxy passes it without problems.
I have tried playing with the bufsize and such, but those have not changed the issue. I can find no specific discussions of this in my searches.
thanks in advance,
jerry