Patch applied, thank you. I have also indicated that the same applies
for the HTTP response. Be careful next time you post a patch, your
mailer corrupts it. Fortunately it was a small one so I could fix it
by hand.
Thanks,
Willy
On 10/21/12 12:06 AM, Willy Tarreau wrote:
On Sun, Oct 21, 2012 at 12:01:10AM +0400, Dmitry Sivachenko wrote:
As I wrote in my original e-mail, I use tune.bufsize=32768. I did not
tweak tune.maxrewrite though.
I will try to decrease maxrewrite to 1024 and see if 'show errors' will
dump more tha
On Sun, Oct 21, 2012 at 12:01:10AM +0400, Dmitry Sivachenko wrote:
> As I wrote in my original e-mail, I use tune.bufsize=32768. I did not
> tweak tune.maxrewrite though.
> I will try to decrease maxrewrite to 1024 and see if 'show errors' will
> dump more that 16k of URL.
>
> I don't fully und
On 10/20/12 11:49 PM, Willy Tarreau wrote:
Hello Dmitry,
On Sat, Oct 20, 2012 at 10:13:47PM +0400, Dmitry Sivachenko wrote:
Hello!
I am using haproxy-1.4.22.
Now I can see the last invalid request haproxy rejected with Bad Request
return code with the following command:
$ echo "show errors" |
Hello Dmitry,
On Sat, Oct 20, 2012 at 10:13:47PM +0400, Dmitry Sivachenko wrote:
> Hello!
>
> I am using haproxy-1.4.22.
> Now I can see the last invalid request haproxy rejected with Bad Request
> return code with the following command:
> $ echo "show errors" | socat stdio unix-connect:/tmp/hap
Hello!
I am using haproxy-1.4.22.
Now I can see the last invalid request haproxy rejected with Bad Request
return code with the following command:
$ echo "show errors" | socat stdio unix-connect:/tmp/haproxy.stats
1) The request seems to be truncated at 16k boundary. With very large
GET requ
6 matches
Mail list logo
