Yes. sometimes I get it and sometimes don't though. As I said this is probably have to do with some other device (hopefully). Another interesting thing is, that we didn't have those kind of requests all the time. It was started soon after changing the configuration from "single listen" to "frontend-backend" config style (we have not try to switch it back though)
On Wed, Dec 26, 2012 at 4:30 PM, Brendon Colby <bren...@newgrounds.com>wrote: > On Dec 26, 2012, at 5:57 PM, SBD <sbd....@gmail.com> wrote: > > We have the same exact problem, only that dontlognull is not working for > us neither for some reason (we have 1 byte requests containing a single > byte - NULL - maybe something affected from a firewall or other device > tunneling the traffic to our LB). > > We also concluded this is something the browsers are doing automatically > (especially when "option http-server-close" is in use). > > If you find any other solution not including the dontlognull option we > would love to hear about it. > > > I remember seeing your e-mail in the archives. Did you get this from > sending "show errors" to the socket? > > > frontend ****** (#1): invalid request > > src ******, session #3468, backend <NONE> (#-1), server <NONE> (#-1) > > HTTP internal state 26, buffer flags 0x00909002, event #0 > > request length 1 bytes, error at position 0: > > > > 00000 \x00 > > I don't see this type of error when I run "show errors" so I'm curious why > you're seeing these and I'm not. > > Brendon >
