Using foo.*.example.com as wilcards

hello. I’m using nginx 0.6.39 and trying to get wildcards like
foo.*.example.com working which according to
http://wiki.nginx.org/NginxVirtualHostExample
should work, but I get “invalid serer name or wildcard” when
attempting to start nginx. nothing in the changelog indicates that a
newer version of nginx would fix this.

Any suggestions on a way to make this work? It’s a rather odd
situation, but .example.com and foo..example.com live on separate
clusters of web servers.

Thanks!

-Chris

Hello!

On Wed, Nov 04, 2009 at 04:00:03PM -0500, Chris Kelly wrote:

hello. I’m using nginx 0.6.39 and trying to get wildcards like
foo.*.example.com working which according to
http://wiki.nginx.org/NginxVirtualHostExample should work, but I get
“invalid serer name or wildcard” when attempting to start nginx.
nothing in the changelog indicates that a newer version of nginx
would fix this.

It shouldn’t work, this wiki example is wrong. Feel free to fix
it.

Wildcards only allowed at start or at end of server name. For
arbitrary matching use regular expressions, see here for details:

http://wiki.nginx.org/NginxHttpCoreModule#server_name

Any suggestions on a way to make this work? It’s a rather odd
situation, but .example.com and foo..example.com live on separate
clusters of web servers.

server_name ~^foo..*.example.com;

Maxim D.

On Nov 4, 2009, at 5:04 PM, Maxim D. wrote:

it.
Wiki example fixed.

Wildcards only allowed at start or at end of server name. For
arbitrary matching use regular expressions, see here for details:

Module ngx_http_core_module

Any suggestions on a way to make this work? It’s a rather odd
situation, but .example.com and foo..example.com live on separate
clusters of web servers.

server_name ~^foo..*.example.com;

This works perfectly. Thanks!