Hello!
On Fri, Apr 04, 2014 at 04:20:04AM -0400, phil3361 wrote:
> Hi all,
>
> The WebSocket protocol specification (RFC 6455) defines a _protocol_level_
> keep alive fonctionnality (the protocol defines both a 'ping' and a 'pong'
> frame).
>
> Unfortunately, it seems that nginx doesn't take th
Hi all,
The WebSocket protocol specification (RFC 6455) defines a _protocol_level_
keep alive fonctionnality (the protocol defines both a 'ping' and a 'pong'
frame).
Unfortunately, it seems that nginx doesn't take these frames into account to
reset its timeout watchdog timer so far... so that you
Thanks for the info.
For 2) , it would be nice to accept value of -1 ( or 0 ) for
proxy_read_timeout as indefinite, namely no timeout checking
at proxy.
On Tue, Jun 4, 2013 at 3:45 AM, Maxim Dounin wrote:
> Hello!
>
> On Mon, Jun 03, 2013 at 03:24:52PM -0700, Alder Network wrote:
>
> > I got
Hello!
On Mon, Jun 03, 2013 at 03:24:52PM -0700, Alder Network wrote:
> I got nginx websocket proxy working but the socket would close
> in a minute or so. So I add
> proxy_read_timeout 180s;
> and it works within 3 minutes but closed the websocket after 3
> minutes, but it works OK before that
I got nginx websocket proxy working but the socket would close
in a minute or so. So I add
proxy_read_timeout 180s;
and it works within 3 minutes but closed the websocket after 3
minutes, but it works OK before that. Why is that?
BTW, I am using Nginx 1.4 now.
Thanks,
- Alder
___
