Hi John.
Am 17-09-2015 07:03, schrieb John Skarbek:
Good Morning!
So recently I went into battle between our CDN provider and our
application team due to some HTTP400's coming from somewhere. At first
I never suspected haproxy to be at fault due to the way I was groking
our logs. The end result is that I discovered haproxy doesn't log the
GET request, but rather only logs a `BADREQ` with a termination state
of
`PR--`. Which based on reading documentation haproxy isn't going to
log
a 414, but instead a 400. I ponder if this is due to something being
truncated forcing haproxy to see a malformed request.
Digging into documentation, I glossed over the fact that the default
buffer size isn't 16k, but actually a lower 8192. Unfortunately my
fault, reading quickly got me to this point. But due to reading
further
the following statement is where I finally have a question; under the
config item tune.maxrewrite:
"...It is generally wise to set it to about 1024. It is automatically
readjusted to half of bufsize if it is larger than that. This means you
don't have to worry about it when changing bufsize"
Please can you post the output of haproxy -vv and the anonymized
configuration, thanks.
[snipp]
BR Aleks
