when client is Internet Explorer 10, the websocket session didn't get
proxy'd to websocket server (websocketpp) other browser
clients work fine.
On Thu, Nov 21, 2013 at 12:48 AM, Maxim Dounin wrote:
> Hello!
>
> On Wed, Nov 20, 2013 at 03:17:11PM -0800, Alder Network wro
Is that a known issue? Any remedy available?
Thanks,
- Alder
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
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 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
___
Say if I want to proxy both websocket (ws) and secure websocket
traffic, would latest version of Nginx support that? What would be
the conf?
Thanks,
- Alder
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
, 2013 at 6:37 PM, Alder Network wrote:
> I am writing a Niginx module that from several of worker threads
> that I created by own, I need to notify Nginx's main thread so
> the main thread (single-threaded nginx) doesn't need to poll
> periodically in timer context. What would
I am writing a Niginx module that from several of worker threads
that I created by own, I need to notify Nginx's main thread so
the main thread (single-threaded nginx) doesn't need to poll
periodically in timer context. What would be the reliable way to
do that in Nginx? Anybody advice would be app
oxy_set_header Upgrade $http_upgrade;
> proxy_set_header Connection $connection_upgrade;
> proxy_pass http://localhost:$proxy_upstream_port;
> }
>
> Partly taken from http://nginx.org/en/docs/http/websocket.html.
>
> appa
>
>
>
> On Thu, May 9, 2013 at 12:35 A
This must have been discussed before but I am new to nginx
and this forum.
I am upgrading to 1.4 to use its websocket proxy feature.
Say I have a websocket server running at port 81, so I want
to forward all websocket packets to port 81, and process
the rest at port 80.
Somehow the following conf
d, May 08, 2013 at 10:17:23AM -0700, Alder Network wrote:
>
> > There seems to be a version dependency on opnessl in ngnix1.4.
> > I can build it on one platform but not the other where there's slightly
> > older version of openssl header files. Specifically,
> > ngx
There seems to be a version dependency on opnessl in ngnix1.4.
I can build it on one platform but not the other where there's slightly
older version of openssl header files. Specifically,
ngx_event_openssl_stapling.c references some constants which are
only defined in newer version of tls1.h. It wo
nin wrote:
> > Hello!
> >
> > On Wed, May 01, 2013 at 11:17:10AM -0700, Alder Network wrote:
> >
> >> Just for clarity, I want to be listening on both IPv4 and IPv6 on the
> same
> >> port.
> >
> > You have to write
> >
> > li
Just for clarity, I want to be listening on both IPv4 and IPv6 on the same
port.
On Wed, May 1, 2013 at 11:00 AM, Alder Network wrote:
> netstat -pln shows the server is waiting on that port.
>
> Yes, I have been using in server section
> listen [::]:80;
> What is supposed
, May 01, 2013 at 10:13:34AM -0700, Alder Network wrote:
>
> > Tried to upgrade to just-released Nginx1.4. TCP 3-way hand-shake
> > aborted by server's ACK+RST packet, but netstat shows server
> > is listening on that port. Any config has been changed since Nginx 1.2
>
Tried to upgrade to just-released Nginx1.4. TCP 3-way hand-shake
aborted by server's ACK+RST packet, but netstat shows server
is listening on that port. Any config has been changed since Nginx 1.2
to 1.4 in this regard?
Thanks,
- Alder
___
nginx mail
15 matches
Mail list logo
