nginx: server_name wildcard not working
Igor Sysoev
is at rambler-co.ru
Fri Jul 6 00:35:41 MSD 2007
On Wed, Jun 27, 2007 at 02:20:24PM +0100, Igor Clark wrote:
> 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?
No, 0.6.0+ supports wildcards at the beginning OR at the end
and as full domain part(s) only. There's no plans to add other
functionality.
> 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
> >wayneseguin at gmail.com
> >
> >
> >
>
> --
> 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/
>
>
--
Igor Sysoev
http://sysoev.ru/en/
More information about the nginx
mailing list