Re: Log 400 bad request

2012-02-13 Thread Sander Klein
Hi Willy, On 13.02.2012 08:07, Willy Tarreau wrote: You won't have it in the log because the request failed to completely parse. Maybe we could improve a bit the error path to be able to report the request URI when only headers fail, that would help. In my case that won't help. I need to

Re: Log 400 bad request

2012-02-12 Thread Willy Tarreau
Hi Sander, On Fri, Feb 10, 2012 at 04:28:39PM +0100, Sander Klein wrote: Hi All, I'm having a small problem with non RFC2616 requests. I would like to log them, but haproxy only logs: cluster1-in cluster1-in/NOSRV -1/-1/-1/-1/0 400 1951 - - PR-- 235/235/0/0/0 0/0 {|||} {} BADREQ Is

Log 400 bad request

2012-02-10 Thread Sander Klein
Hi All, I'm having a small problem with non RFC2616 requests. I would like to log them, but haproxy only logs: cluster1-in cluster1-in/NOSRV -1/-1/-1/-1/0 400 1951 - - PR-- 235/235/0/0/0 0/0 {|||} {} BADREQ Is there a way to log them with the full host header and URL? I know I can show