12 May '13, 8pm

Feeding a looooong URL to nginx? Careful there.

On Mon, Oct 29, 2012 at 07:43:27PM -0400, B.R. wrote: Hi there, > When submitting too large requests, Nginx replies a page containing the > right code status but serves the errors page with a HTTP/0.9 (!) 200 answer. No, it doesn't. Look at the "curl -i" output. Your browser is making up the 200 status. It is right about the HTTP/0.9 response, though, because nginx couldn't see that the request was HTTP/1.0 or HTTP/1.1. And therefore it "knows" that it was HTTP/0.9. See the thread including http://forum.nginx.org/read.php?2,228425,228431 for more details. I think that nginx is not wrong in this case. But I also think that it wouldn't be wrong if this HTTP/0.9 response had two paragraphs, and began with the characters "HTTP/1.1 414". I imagine that if someone provided a justification with a patch, it would be considered like any other suggested patch. f -- Francis Daly fran...

Full article: http://www.ruby-forum.com/topic/4407280

Tweets

Gehirn RS2 に nginx + unicorn 環境で Rails3 を動かしてみる...

qiita.com 11 May '13, 11am

upstream backend-unicorn { server 127.0.0.1:3000; } server { listen 61***; # Gehirn のプロキシ先ポート番号 server_name yourname.gehir...

ASCIIcast 414 - Batch API Requests (pro)

railscasts.com 12 May '13, 9pm

Apr 27, 2013 | 18 minutes | Rack , APIs Here I demonstrate how to perform bulk API operations though a single request usin...