On Wednesday 17 December 2014 17:55:44 tom123 wrote:
> Hi Nginx experts,
>
> i am looking for a way to limit connections per ip for proxied websockets
> through nginx. I found the ngx_http_limit_conn_module settings in the
> manual. But i am not sure if this works also for proxied websockets. Does
Hi Nginx experts,
i am looking for a way to limit connections per ip for proxied websockets
through nginx. I found the ngx_http_limit_conn_module settings in the
manual. But i am not sure if this works also for proxied websockets. Does
anyone have a suggestion? I am on the right track?
http://ngi
After analysing the data stream, Nginx is indeed streaming the data. The
difference is Nginx is buffering it into one continuous stream, where as the
data from the browsers is fragmented.
The websocket implementation I was using needed fixing.
Posted at Nginx Forum:
http://forum.nginx.org/read.p
Logs?
---
*B. R.*
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Connecting to my websocket server directly works (Chrome or Firefox).
Connecting via the Nginx websocket proxy connects, but drops frames. Here is
an example of the JSON messages:
<-- {"login" : { "username": "user", "password" : "pass"}}
--&
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
Hello!
On Thu, Nov 21, 2013 at 02:12:47PM -0800, Alder Network wrote:
> when client is Internet Explorer 10, the websocket session didn't get
> proxy'd to websocket server (websocketpp) other browser
> clients work fine.
Works fine here, just tested:
192.168.56.1 - - [22/Nov/2013:16:48:39 +040
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 wrote:
>
> > Is that a kno
Hello!
On Wed, Nov 20, 2013 at 03:17:11PM -0800, Alder Network wrote:
> Is that a known issue? Any remedy available?
What's the issue?
--
Maxim Dounin
http://nginx.org/en/donation.html
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/
Is that a known issue? Any remedy available?
Thanks,
- Alder
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
>
> > 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?
> > B
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
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
Thanks for the recipe.
Just tried and now I am not able to get regular
HTTP working on port 80.
Has anybody ever got nginx websocket proxy working?
Thanks,
- Alder
On Thu, May 9, 2013 at 11:19 AM, António P. P. Almeida wrote:
> At the http level:
>
> map $htt
t 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 followin
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
There is a commit from maxim about ~12hs ago >
http://trac.nginx.org/nginx/changeset/5073/nginx :)
On Mon, Feb 18, 2013 at 10:06 AM, Andrew Alexeev wrote:
> On Feb 18, 2013, at 4:03 PM, perone wrote:
>
> > Is there any updates on the Websocket proxy support ? Everything I foun
On Feb 18, 2013, at 4:03 PM, perone wrote:
> Is there any updates on the Websocket proxy support ? Everything I found is
> only this: http://trac.nginx.org/nginx/milestone/1.3.13
Yes, there will be an update very soon. Be patient and stay
Is there any updates on the Websocket proxy support ? Everything I found is
only this: http://trac.nginx.org/nginx/milestone/1.3.13
Thank you !
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,236289,236289#msg-236289
___
nginx mailing list
20 matches
Mail list logo
