<font color="#333399"><font><font>To avoid saying odd things, the only think I am <font>sure of when I checked the exception output from <font>P</font>ython is that it started with '<html>'</font></font>. Maybe the rest of the output ca<font>me from my script.<br>
<font>I am not at work any more I can't check.<br><br><font>The only thing I am pretty sure about is that the status must be a status like '200 OK' or '414 <font>WTH<font>AreYouDoin<font>'</font></font></font></font></font></font></font></font>.<br>
<font>I hate P<font>ython, but I'll trust it on that one ^^<br><br><font>I'll try to make a little PoC if needed,</font><br clear="all"></font></font><font size="1"><span style="color:rgb(102,102,102)">---<br></span><b><span style="color:rgb(102,102,102)">B. R.</span></b><span style="color:rgb(102,102,102)"></span></font><br>
<br><br><div class="gmail_quote">On Mon, Oct 29, 2012 at 8:57 PM, B.R. <span dir="ltr"><<a href="mailto:reallfqq-nginx@yahoo.fr" target="_blank">reallfqq-nginx@yahoo.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<font color="#333399"><font>@Valentin<br><font>I am not seeking <font>a solution to the 414 problem, I know how to address the issue</font></font><br><font>Thanks anyway<br><br><font>@<font>Francis<br>T<font><font>he <font>browser output has just be made to illustrate the wrong answer<font>.<br>
<font><br>The problem triggered using</font> a Python script which checked against the 'status' field of a HTTP <font>answer to decide on its actions.<br><font>It crashed several times at random occurences<font> with a BadStatusLine <font>exception.<br>
<font>The <font>exception m<font>essage</font> was something like '<html>\n\n\n\n200'<font>.<br></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font></font><br clear="all">
<font color="#333399"><font><font><font><font>I do not know the <font>implementation details<font>, although I suspect <font>a<font>n answer code should be an answer code.<br><font>I didn't get 414, I get something which made my script crash.<br>
<br><font>That's why I guess that's a bug</font></font></font></font></font></font></font></font></font></font></font><font size="1"><span style="color:rgb(102,102,102)"><br>---<br></span><b><span style="color:rgb(102,102,102)">B. R.</span></b></font><div>
<div><font color="#333399"><font><font><font><font><font><font><font><font><font><font></font><br>
</font></font></font></font></font></font></font></font></font></font><br><br><div class="gmail_quote">On Mon, Oct 29, 2012 at 8:12 PM, Francis Daly <span dir="ltr"><<a href="mailto:francis@daoine.org" target="_blank">francis@daoine.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Mon, Oct 29, 2012 at 07:43:27PM -0400, B.R. wrote:<br>
<br>
Hi there,<br>
<div><br>
> When submitting too large requests, Nginx replies a page containing the<br>
> right code status but serves the errors page with a HTTP/0.9 (!) 200 answer.<br>
<br>
</div>No, it doesn't.<br>
<br>
Look at the "curl -i" output.<br>
<br>
Your browser is making up the 200 status.<br>
<br>
It is right about the HTTP/0.9 response, though, because nginx couldn't<br>
see that the request was HTTP/1.0 or HTTP/1.1. And therefore it "knows"<br>
that it was HTTP/0.9.<br>
<br>
See the thread including <a href="http://forum.nginx.org/read.php?2,228425,228431" target="_blank">http://forum.nginx.org/read.php?2,228425,228431</a><br>
for more details.<br>
<br>
I think that nginx is not wrong in this case. But I also think that it<br>
wouldn't be wrong if this HTTP/0.9 response had two paragraphs, and began<br>
with the characters "HTTP/1.1 414".<br>
<br>
I imagine that if someone provided a justification with a patch, it<br>
would be considered like any other suggested patch.<br>
<span><font color="#888888"><br>
f<br>
--<br>
Francis Daly <a href="mailto:francis@daoine.org" target="_blank">francis@daoine.org</a><br>
</font></span><div><div><br>
_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org" target="_blank">nginx@nginx.org</a><br>
<a href="http://mailman.nginx.org/mailman/listinfo/nginx" target="_blank">http://mailman.nginx.org/mailman/listinfo/nginx</a><br>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br>