400 response ...
alan at blog-city.com
Mon Jul 14 12:24:55 MSD 2008
interesting, i had to restart the service here to get this logging
enabled; a simply HUP didn't work.
okay, back to this though -- what makes nginx throw a 400 response?
in the error log i get lots of these:
2008/07/14 08:22:09 [info] 9392#0: *54478 client 126.96.36.199 closed
2008/07/14 08:22:09 [info] 9391#0: *55972 client 188.8.131.52 closed
2008/07/14 08:22:09 [info] 9391#0: *55981 client 184.108.40.206 closed
some of these:
2008/07/14 08:22:10 [warn] 9392#0: *56100 an upstream response is
buffered to a temporary file /usr/local/nginx/proxy_temp/1/35/0000000351
while reading upstream, client: 220.127.116.11, server:
rss.feedsportal.com, request: "GET /c/269/f/3544/index.rss HTTP/1.1", u
very few of these:
2008/07/14 08:23:53 [info] 9392#0: *105147 client timed out (110:
Connection timed out) while reading client request line, client:
18.104.22.168, server: 0.0.0.0:80
Yet we get TONS of 400's being reported in the access logs.
What happens if a backend isn't able to process a connection? Does
nginx not through a 503 instead?
Igor Sysoev wrote:
> On Fri, Jul 04, 2008 at 03:50:47PM +0100, Alan Williamson wrote:
>>>> We are using nginx as a frontend loadbalancer, but our code does not
>>>> generate 400 errors. So under what circumstances would nginx return a
>>>> 400 request?
>>> Reasons of these errors are logged at info level in error_log:
> The default level is notice.
> Unimportant client errors are logged at info level.
More information about the nginx