nginx not completly http/1.1 compliant?

[Igor Sysoev]

On Wed, Feb 04, 2009 at 05:28:31PM +0100, Marlon de Boer wrote:

> Hi list,
> 
> If I request the following url
> 
> GET ?var=something HTTP/1.1
> host: somehost.com
> 
> Nginx returns an error saying 400 Bad Request.
> 
> According to
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec5.html#sec5.1.2 "Note
> that the absolute path cannot be empty; if none is present in the
> original URI, it MUST be given as "/" (the server root)."

As I understand this sentence, this means that a client MUST send
absolute path.

> I'm running 0.6.29, looked at the changelog for all stable releases but
> saw no fixes for this, is this a bug? or is the above GET request
> officially incorrect?
> 
> Regards
> Marlon


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