On 24 August 2011 12:12, Thomas Love <tomlove@gmail.com> wrote:
> On 24 August 2011 12:09, Maxim Dounin <mdounin@mdounin.ru> wrote:
>
>> Error 502 suggests it's not nginx timeout (error will be 504 then)
>> but backend's one.
>>
>> Maxim Dounin
>
> Thanks. I thought it might be. I'm scouring node...
>
> Thomas
>

Found it. For any other node fanboys: there's a hardcoded 120-second
idle timeout in node.js's http.js, and to change it, call

request.socket.setTimeout(seconds * 1000);

Thomas

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx