On Wed, 2011-01-19 at 06:35 +0100, Willy Tarreau wrote: > Hello Kristian,
[snipped] > As you can see, an invalid request (400) was reported by haproxy. > Haproxy supports 64-bit content lengths, so I don't see why that would > not work even with large files. Are you sure that your client does > support large content-lengths and that it is not sending a negative > value due to an integer overflow ? Yes. I believe it's a client error. We've tracked down a lack of content-length header and a keep-alive request. > > Can anyone point us to a solution? > > You should add the following line to your HTTP frontend : > > capture request header Content-Length len 20 > > The content-length header will then appear in the logs between > braces. Thanks for the tip. > Regards, > Willy
