<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>There is no bug in Rails neither in Webserver!</div><div>It's a bug on passenger module implementation.</div><div><br></div><div>Anatoly</div><div><br><blockquote type="cite"><div dir="ltr">That was a bug in rails not the web server.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Feb 13, 2013 at 11:30 AM, Anatoly Mikhailov <span dir="ltr"><<a href="mailto:anatoly@sonru.com" target="_blank">anatoly@sonru.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><div><br></div><blockquote type="cite">I'm struggling to find the source of a timeout. I am running Nginx (1.2.6),<br>
Passenger 3.0.18, and Rails 3.2.11. On serving one long running request, I<br>find the results (CSV file) truncated after being returned from the client.<br>The Rails application however continues to serve up the data until complete,<br>
at which time it reports:<br><br> Couldn't forward the HTTP response back to the HTTP client: It seems the<br>user clicked on the 'Stop' button in his browser.<br><br>Nginx access.log however reports a 200 for the request.<br>
<br>Some things I have tried:<br>1) I modified the Nginx read/send timeouts in the Passenger gem<br>(ext/nginx/Configuration.c) and recompiled, with no impact.<br>2) I ran a test of bypassing Nginx/Passenger by going direct to my app<br>
running in Unicorn, and it serves up the result fine. I then took Passenger<br>out of the equation by configuring Nginx to pass the requests to Unicorn,<br>and the truncated result is back again.<br>3) I've played with the Nginx keepalive_timeout, proxy_read_timeout,<br>
proxy_send_timeout and send_timeout - all with no impact.<br><br>Any thoughts/advice would be much appreciated.<br><br>Joe<br><br>Posted at Nginx Forum: <a href="http://forum.nginx.org/read.php?2,236201,236201#msg-236201" target="_blank">http://forum.nginx.org/read.php?2,236201,236201#msg-236201</a><br>
<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>
</blockquote></div><br><div>It happened for us many times, there is only one option - <b>upstream</b>.</div><div>It can be Unicorn/PassengerStandalone/whatever.</div><div><br></div><div>We spent a lot of time debugging Nginx, so there is no real solution </div>
<div>for passenger built-in module.</div><span class="HOEnZb"><font color="#888888"><div><br></div><div><br></div><div>Anatoly</div><div><br></div></font></span></div><br>_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org">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></blockquote></div><br></div>
_______________________________________________<br>nginx mailing list<br><a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>http://mailman.nginx.org/mailman/listinfo/nginx</blockquote></div></body></html>