400 response ...

[Igor Sysoev]

On Fri, Jul 04, 2008 at 02:23:46PM +0100, Alan Williamson wrote:

> We are getting an awful lot of 400 responses being sent back to our clients.
> 
> For example, consider these two, first one resultsed in a 400, where as 
> the second one didn't.
> 
> 79.a.c.d - - [04/Jul/2008:13:14:21 +0000] GET /sportbladet/?service=rss 
> HTTP/1.1 "400" 173 "-" "Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; 
> en-US; rv:1.9) Gecko/2008061004 Firefox/3.0" "-"
> 
> 79.a.c.d - - [04/Jul/2008:13:14:22 +0000] GET /sportbladet/?service=rss 
> HTTP/1.1 "200" 18003 "-" "Mozilla/5.0 (Macintosh; U; Intel Mac OS X 
> 10.4; en-US; rv:1.9) Gecko/2008061004 Firefox/3.0" "-"
> 
> 
> 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:

error_log  /path/to/log  info;


-- 
Igor Sysoev
http://sysoev.ru/en/