Still having HTTP 400 - nginx bad request error

Wed Aug 13 23:30:42 MSD 2008

On Wed, Aug 13, 2008 at 11:24:28PM +0400, Igor Sysoev wrote:

> On Wed, Aug 13, 2008 at 12:14:57PM -0700, mike wrote:
> 
> > On 8/13/08, Igor Sysoev <is at rambler-co.ru> wrote:
> > 
> > > nginx accepts any character in URL except space. I do not think that
> > > unescaped spaces are common: I have just seen www.rambler.ru's last
> > > 400,000 requests. There are 50 line with 400 errors and no one with space.
> > >
> > > Probably these spaces are bugs in mobile phones.
> > >
> > > Apache 1.3 returns 400 for such URLs too, while modern Apache2 accepts them.
> > 
> > okay, so anyone with a buggy mobile phone loading an nginx site is
> > just out of luck? instead of probably a minor check for a " " in the
> > url and encoding it for them?
> 
> I will look.
> 
> BTW, the buggy mobile phone owners are unhappy with google too:
> 
> -----------
> >nc www.google.com 80 | head -10
> GET /search?q=test test HTTP/1.0
> 
> HTTP/1.0 400 Bad Request
> Date: Wed, 13 Aug 2008 19:23:35 GMT
> Content-Type: text/html; charset=UTF-8
> Server: GFE/1.3
> Connection: Close
> Content-Length: 1344
> 
> 
> 
> <html><head>
> 
> 
> <html><head>
> <meta http-equiv="content-type" content="text/html;charset=utf-8">
> <title>400 Bad Request</title>
> -------------

Thus, the buggy mobile phone owners are unhappy with google, Yahoo,
facebook (both run Apache 1.3), microsoft.com, and msn.com.

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