Thanks Willy!
I recompile haproxy with:
"-DBUFSIZE=16000 -DMAXREWRITE=1024 -DSYSTEM_MAXCONN=40000"
It doesn't work. Then I recompile with:
"-DBUFSIZE=64000 -DMAXREWRITE=1024 -DSYSTEM_MAXCONN=40000"
And it works. But I'm very worried about this value. This is the
difference in haproxy logs:
DBUFSIZE=default
Jan 7 20:07:41 127.0.0.1 haproxy[15042]: X.X.X.X:36464
[07/Jan/2010:20:07:41.338] main bdefault/proxy1 111/0/0/-1/182 502
8396 - - PHVN 0/0/0/0/0 0/0 {1643} "POST /user/config HTTP/1.1"
DBUFSIZE=64000
Jan 7 20:14:42 127.0.0.1 haproxy[15129]: X.X.X.X:31434
[07/Jan/2010:20:14:41.531] main bdefault/proxy1 104/0/0/586/1206 200
46025 - - --VN 0/0/0/0/0 0/0 {102721} "POST /user/config HTTP/1.1"
"show errors" doesn't show anything after the 502 (show info and show
stat are working fine).
So i'm going to test BUFSIZE=64000 very carefully. Meanwhile i'm
checking why the headers are so big. I know haproxy can capture
headers, but it seems can not capture all so I don't know where to
start.
Thanks again,
Héctor
On Thu, Jan 7, 2010 at 5:07 PM, Willy Tarreau <[email protected]> wrote:
> Be careful with large headers, there are many equipments which don't
> accept them or which partially fail on them. Also, large cookies are
> painful for users because they have to emit them for all requests,
> which can make them upload megs of data for a few tens of objects.
