Finally, Nginx 1.3.13 supports websocket officially.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,221884,237425#msg-237425
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
I haven't tried it yet, but nginx-push-stream-module looks good:
https://github.com/wandenberg/nginx-push-stream-module
_Nik
On 3/15/2013 4:24 PM, djczaski wrote:
> What are the best options for websocket backends? I'm working with an
> embedded platform so I'm somewhat restricted to something l
> In case of https, in many (most) cases there are pending data -
> due to various SSL packets send during connection close. This
> means connection close detection with https doesn't work unless
> you use kqueue.
>
> Further reading:
>
> http://mailman.nginx.org/pipermail/nginx/2011-June/02
I also just tried the ip_hash module and it also disables the keepalive
functionality :(
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,237417,237420#msg-237420
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/
I've been trying to get this setup working:
client <- c0 -> nginx1 <- c1 -> nginx2 <- c2 -> service (http)
where the c1 connection is kept alive between request from from the outside,
but c0 and c2 are closed after each request. I've used the 'keepalive'
keyword in the upstream nginx1 config, and
Well, true, but .mov is still h.264 encoded, so I believe it would still use
the same streaming mechanism. Maybe I'm wrong about that. At any rate, it
appears to be working now that I fixed my nginx location filters.
Lukas Tribus Wrote:
---
> .
Once again, never mind. I had a bad location filter.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,237411,237415#msg-237415
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
.mov is not .mp4, they are completely different containers.
> To: nginx@nginx.org
> Subject: Nginx 1.2.7 / h.264 / flowplayer
> From: nginx-fo...@nginx.us
> Date: Fri, 15 Mar 2013 13:30:50 -0400
>
> I'm running Nginx v1.2.7 from the Nginx repo, with mp4
I'm running Nginx v1.2.7 from the Nginx repo, with mp4 module enabled.
I added this to my conf:
location ~ \.mov {
mp4;
mp4_buffer_size 1m;
mp4_max_buffer_size 5m;
}
location / {
try_files $uri $uri/ @rewrite;
Never mind, I guess there are two configure statements in the spec file. I
added the module to both and it's working fine.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,237384,237409#msg-237409
___
nginx mailing list
nginx@nginx.org
http://
> From: "Reddirt"
> I got past that error and now the nginx error log has this:
>
> 2013/03/14 14:22:10 [error] 1537#0: *1 connect() failed (111: Connection
> refused) while connecting to upstream, client: 192.168.20.3, server: ,
> request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:3000/";,
Hello!
On Fri, Mar 15, 2013 at 06:35:27AM -0400, ilmerovingio wrote:
> Hi, I've a few servers with nginx 1.2.3 that run a streaming services
> platform.
>
> Is there in nginx any "read_timeout" directive (like the send_timeout but
> for the opposite) that shuts down the connection if the client
thanks, i will try as you mention and report it on forum.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,237393,237397#msg-237397
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hi, I've a few servers with nginx 1.2.3 that run a streaming services
platform.
Is there in nginx any "read_timeout" directive (like the send_timeout but
for the opposite) that shuts down the connection if the client has not send
any data for x time?
I'm looking for something also in beta stage,
Hello!
On Fri, Mar 15, 2013 at 04:39:03AM -0400, honwel wrote:
> hi
> on centos 6, nginx-1.2.2, nginx was compiled with:
> --prefix=/usr/local/nginx --user=root --group=root --with-http_ssl_module
> --with-ipv6 --with-pcre=/home/nginx/src/pcre-8.20
> --with-openssl=/home/nginx/src/openssl-1.0
Hello!
On Fri, Mar 15, 2013 at 04:24:13AM -0400, varan wrote:
> I mean I haven't got full list of ip addresses that can be proxy, so I want
> nginx to look X-FORWARDED-FOR header for any ip address, and if the header
> exists to determine geo using the header. If there's no X-Forwarded-For
> head
hi
on centos 6, nginx-1.2.2, nginx was compiled with:
--prefix=/usr/local/nginx --user=root --group=root --with-http_ssl_module
--with-ipv6 --with-pcre=/home/nginx/src/pcre-8.20
--with-openssl=/home/nginx/src/openssl-1.0.1c
--with-zlib=/home/nginx/src/zlib-1.2.7
--add-module=/home/nginx/svn/ngi
I mean I haven't got full list of ip addresses that can be proxy, so I want
nginx to look X-FORWARDED-FOR header for any ip address, and if the header
exists to determine geo using the header. If there's no X-Forwarded-For
header, then use ip address for geo.
is it acceptable to use "proxy 0.0.0.0/
Hello!
On Thu, Mar 14, 2013 at 07:07:20PM -0700, Jay Oster wrote:
[...]
> The access log has 10,000 lines total (i.e. two of these tests with 5,000
> concurrent connections), and when I sort by upstream_response_time, I get a
> log with the first 140 lines having about 1s on the upstream_respons
are you able to fetch the given ressource from your nginx-server?
e.g. wget https://127.0.0.1:4443/socket.io/socket.io.v0.9.11.js
maybe you have an port-issue (4443 vs 443)
mex
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,237385,237390#msg-237390
_
Hello!
On Fri, Mar 15, 2013 at 03:22:31PM +1100, Robert Mueller wrote:
[...]
> When using http with my test client, I see this in the nginx log when
> the client disconnects:
>
> 2013/03/14 23:27:27 [info] 27717#0: *1 client prematurely closed
> connection, so upstream connection is closed too
21 matches
Mail list logo
