Hi Willy,
Thanks for the patch! I have now confirmed that it works fine for us. On Tue, Jul 30, 2013 at 11:10 AM, Willy Tarreau <[email protected]> wrote: > Most servers and intermediaries do not support 2GB chunks (at least last > time I checked). Chunked encoding was made for contents you don't know > the length before sending, so that suggests the sender is filling a buffer > and sending it. I was already surprized that some applications might want > to buffer up to 256MB before starting to send (especially HTML which is > slow to produce), 2GB is even less likely. > I agree completely. I was also quite surprised when I learned of this :) > If the statement in the patch is still correct even for 1.5 ("increasing > the > > limit past 2 GB causes trouble due to some 32-bit subtracts in various > > computations becoming negative (eg: buffer_max_len)", perhaps we can > document > > this somewhere? Seems frustrating to let the users discover this on his > own. > > Yes I agree with you. > Besides the very welcome documentation update, don't you think that currently HAProxy is handling the situation in a surprising way (returning an empty response with status code 200)? There are of course the "PD" termination flags on the log line, but I would also expect some 5xx status code to be given to the client when an internal error happens in HAProxy. Best regards, -- Kristjan Koppel
