atom feed8 messages in ru.sysoev.nginxRe: nginx: server_name wildcard not w...
FromSent OnAttachments
Igor ClarkJun 27, 2007 4:00 am 
Wayne E. SeguinJun 27, 2007 4:59 am 
Igor ClarkJun 27, 2007 6:20 am 
Wayne E. SeguinJun 27, 2007 6:53 am 
Igor ClarkJun 27, 2007 7:14 am 
Igor SysoevJul 5, 2007 1:35 pm 
Igor SysoevJul 5, 2007 1:36 pm 
Igor ClarkJul 9, 2007 2:36 am 
Subject:Re: nginx: server_name wildcard not working
From:Igor Clark (igor@public.gmane.org)
Date:Jun 27, 2007 6:20:01 am
List:ru.sysoev.nginx

Thanks Wayne.

I've tried with 0.6 and that allows wildcards at the end, but apparently not at the beginning *and* the end.

# /usr/local/nginx-0.6.0/sbin/nginx -t -c /usr/local/nginx-0.6.0/ conf/nginx.conf 2007/06/27 14:14:24 [emerg] 8819#0: invalid server name or wildcard "*.apache1.*" on 0.0.0.0:80

Should this work in 0.6.0? If not, will it ever work?

Cheers, Igor

On 27 Jun 2007, at 12:59, Wayne E. Seguin wrote:

On Jun 27, 2007, at 07:01 , Igor Clark wrote:

Hi there,

We have developers working with various versions of web servers and programming languages, for different clients and environments. I'm trying to do this:

server { listen 80; server_name apache1 *.apache1.*.mydomain.com;

From what I understand wildcards may be only in front, and the 0.6 branch will allow wildcards at the end.

http://wiki.codemongers.com/NginxHttpMapModule?highlight=%28%2A.%29

-- Wayne E. Seguin Sr. Systems Architect & Systems Admin wayn@public.gmane.org

-- Igor Clark // POKE // 10 Redchurch Street // E2 7DD // +44 (0)20 7749 5355 // www.pokelondon.com

We've gone sub-zero with the TopGear Cool Wall: http:// www.topgear.com/coolwall/