Nginx answers too large requests with bad status

[B.R.]

Alright, I got it now.
That's because the protocol defines its version after the request
address... which is already too long to be fully read.

Thanks for your help!
No bug in Nginx indeed :o)

I'll go set up better buffers,
---
*B. R.*


On Tue, Oct 30, 2012 at 5:17 AM, Valentin V. Bartenev <ne at vbart.ru> wrote:

> On Tuesday 30 October 2012 04:57:40 B.R. wrote:
> > @Valentin
> > I am not seeking a solution to the 414 problem, I know how to address the
> > issue
> > Thanks anyway
> >
> > @Francis
> > The browser output has just be made to illustrate the wrong answer.
> >
> > The problem triggered using a Python script which checked against the
> > 'status' field of a HTTP answer to decide on its actions.
> > [...]
>
> There's no Status-Line in HTTP/0.9. So, the problem is that your script do
> not
> support HTTP/0.9.
>
>  wbr, Valentin V. Bartenev
>
> --
> http://nginx.com/support.html
> http://nginx.org/en/donation.html
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20121030/ecf84a33/attachment.html>