Re: IPv4 & IPv6

Hello, It seems I solved the problem... It was indeed by reading a little more carefully the doc http://wiki.nginx.org/HttpCoreModule#listen, thanks @Lukas! ;o) The '*:80' syntax is used for IPv4 listening, I don't understand why it works as-is for you Ted. Maybe Maxim will be of a better help on

Re: [openresty-en] Re: [ANN] ngx_openresty devel version 1.2.7.3 released

Hello! On Fri, Apr 5, 2013 at 7:02 PM, Bearnard Hibbins wrote: > * Known issues: >"Server" header still says 1.2.7.1 but is actually 1.2.7.3 I cannot reproduce it on my side: $ curl -i localhost/lua HTTP/1.1 200 OK Server: ngx_openresty/1.2.7.3 Date: Sat, 06 Apr 2013 05:13:54

Re: limit proxy_next_upstream

I agree. The directive name and format are always the diffcult parts.[?] I thought we could add a new parameter to the proxy_next_upstream directive. The individual directive is OK for me. Limit the retry total time is great. It could eliminate some very long timeout responses. 2013/4/6 Maxim D

Re: IPv4 & IPv6

Hmm... @Maxim I guess I haven't understood your piece of advice, since 'listen' can only be used in 'server' directive... What is it you wanted me to try, again? :oD --- *B. R.* On Fri, Apr 5, 2013 at 8:02 PM, B.R. wrote: > I have indeed several virtual servers. > > I have a specific one which

Re: IPv4 & IPv6

I have indeed several virtual servers. I have a specific one which serves different content whether a client connects in HTTP or HTTPS (basically the HTTP content provides directions for the HTTPS setup). I also have one virtual server which I want listening on IPv4 only, not IPv6. That's why I p

Re: IPv4 & IPv6

On Apr 5, 2013, at 6:07 PM, B.R. wrote: > @Ted > I​ tested your solution but as I expected nginx is only listening on IPv4 > interfaces after restart and not IPv6 ones anymore.​ Weird. I have this: listen 443 ssl; listen [::]443 ipv6only=on ssl; But aside from

Re: IPv4 & IPv6

Hello! On Fri, Apr 05, 2013 at 06:07:23PM -0400, B.R. wrote: > Hello, > > @Maxim > I tried the duplicate configuration entries: > listen 80; > listen [::]:80 ipv6only=on; > > I has the following error: > nginx: [emerg] duplicate listen options for [::]:80 in > /etc/nginx/conf.d/***.conf:3 If y

Re: IPv4 & IPv6

Hello, @Maxim I tried the duplicate configuration entries: listen 80; listen [::]:80 ipv6only=on; I has the following error: nginx: [emerg] duplicate listen options for [::]:80 in /etc/nginx/conf.d/***.conf:3 @Ted I​ tested your solution but as I expected nginx is only listening on IPv4 interfac

RE: IPv4 & IPv6

Everything you need to know: http://nginx.org/en/docs/http/ngx_http_core_module.html#listen ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: IPv4 & IPv6

On Apr 5, 2013, at 4:17 PM, "B.R." wrote: > Is there any other way to allow Nginx ot listen on both interface types > without mandatory system configuration? I just have "listen *:80" in my configurations, and it works fine over IPv4 and IPv6. ___ ng

Re: IPv4 & IPv6

Hello! On Fri, Apr 05, 2013 at 04:17:09PM -0400, B.R. wrote: > Hello, > > I noticed in an article dedicated to the subject > (Fr)that > to allow Nginx to listen both on IPv4 and IPv6 interfaces > simultaneously, you needed to

Re: limit proxy_next_upstream

Hello! On Fri, Apr 05, 2013 at 09:59:29PM +0800, Weibin Yao wrote: > We have the similar request. If we have dozens of servers in a same > upstream block, I don't want to retry all of them. One side effect is it > will increase the failure count with all of the backend servers. After > several ti

IPv4 & IPv6

Hello, I noticed in an article dedicated to the subject (Fr)that to allow Nginx to listen both on IPv4 and IPv6 interfaces simultaneously, you needed to set sysctl with the following configuration (otherwise Nginx listening bin

Re: nginx keeps crashing

Hello! On Fri, Apr 05, 2013 at 10:13:24AM -0400, ankurs wrote: > Hello, > > Thanks Maxim for looking into my issue. > > I recompiled nginx with no 3rd party module & debugging enabled. > > [root@localhost sbin]# ./nginx -V > nginx version: nginx/1.2.8 > built by gcc 4.4.7 20120313 (Red Hat 4.

RE: nginx keeps crashing

> there is no nginx.core file found in /home/core/ , thats the path specified > in nginx.conf Make sure: - /home/core/ is writable (chmod a+w) - ulimit is configured correctly - fs.suid_dumpable is ok? You can read more about it here: http://www.cyberciti.biz/tips/linux-core-dumps.html

Re: nginx keeps crashing

Hello, Thanks Maxim for looking into my issue. I recompiled nginx with no 3rd party module & debugging enabled. [root@localhost sbin]# ./nginx -V nginx version: nginx/1.2.8 built by gcc 4.4.7 20120313 (Red Hat 4.4.7-3) (GCC) configure arguments: --with-http_stub_status_module --with-http_perl_

Re: How can I limit the total speed of a port or domain name?

How do you test the limit_speed module? It works in my test box. Thanks. 2013/4/5 tssungeng > centos5.5 + nginx-1.3.14 > > I use the limit_speed_zone > (https://github.com/yaoweibin/nginx_limit_speed_module),and set the > nginx.conf: > > http { > limit_speed_zone one $server_port 10m; >

Re: limit proxy_next_upstream

We have the similar request. If we have dozens of servers in a same upstream block, I don't want to retry all of them. One side effect is it will increase the failure count with all of the backend servers. After several times, all of the servers will be marked down for a while and all of the reques

Re: Rewrite "break" directive - a strange behavior

Thank you very much for the immediate answer !! :) Just reading this documentation ("http://nginx.org/en/docs/http/ngx_http_rewrite_module.html#rewrite";) i had the suspect that "set" is a rewrite module`s directive. But, in this other documentation ("http://wiki.nginx.org/HttpRewriteModule#rewri

Re: SPDY + proxy cache static content failures

On Thursday 04 April 2013 02:43:15 spdyg wrote: > No there's nothing in the error log. Access log shows 304's for all > requests that failed. > Could you provide a debug log for the issue? Here is the guide: http://nginx.org/en/docs/debugging_log.html wbr, Valentin V. Bartenev -- http://ngin

Re: inconsistent upstream_addr log

Hello! On Fri, Apr 05, 2013 at 04:44:11AM -0400, philipp wrote: > My log format looks like this > > log_format vcombined '$host $remote_addr - $remote_user [$time_local] > "$request" ' > '$status $body_bytes_sent "$http_referer" ' > '"$http_us

Re: limit proxy_next_upstream

Hello! On Fri, Apr 05, 2013 at 04:38:36AM -0400, philipp wrote: > Is it possible to limit the amount of upstreams asked? I have four upstreams > defined and it makes no sense to ask all of them. If two of them timeout or > error there is possible something wrong with the request and asking anothe

Re: Rewrite "break" directive - a strange behavior

Hello! On Fri, Apr 05, 2013 at 05:38:22AM -0400, andrea.mandolo wrote: > Hi, > > I'd like to report a strange behaviour of REWRITE "break" directives inside > a "location" block, when it is used a SET directive subsequently. > > Now, i quote a little example, with a basic Nginx configuration th

Re: Rewrite "break" directive - a strange behavior

Sorry, i forgot to post Nginx version and build details. NGINX_VERSION="1.2.6" # CONFIGURE command used to build ### ./configure --conf-path=/etc/nginx/nginx.conf --prefix=/etc/nginx --error-log-path=/var/log/nginx/error.log \ --http-client-body-temp-path=/var/lib/nginx/body --htt

Rewrite "break" directive - a strange behavior

Hi, I'd like to report a strange behaviour of REWRITE "break" directives inside a "location" block, when it is used a SET directive subsequently. Now, i quote a little example, with a basic Nginx configuration that simulate the issue. # /etc/nginx/nginx.conf ## worker_processes aut

inconsistent upstream_addr log

My log format looks like this log_format vcombined '$host $remote_addr - $remote_user [$time_local] "$request" ' '$status $body_bytes_sent "$http_referer" ' '"$http_user_agent" "$http_x_forwarded_for" ' '$ssl_cipher $reques

limit proxy_next_upstream

Is it possible to limit the amount of upstreams asked? I have four upstreams defined and it makes no sense to ask all of them. If two of them timeout or error there is possible something wrong with the request and asking another node doesn't help. Posted at Nginx Forum: http://forum.nginx.org/rea

Re: How can I limit the total speed of a port or domain name?

On Thu, Apr 04, 2013 at 10:29:01PM -0400, tssungeng wrote: Hi there, > I use the limit_speed_zone > (https://github.com/yaoweibin/nginx_limit_speed_module),and set the > nginx.conf: Ok, this third party module looks like it should do what you want, according to its description. > http { > l