Re: [users@httpd] apache 2.4 virtualhosts

2012-03-16 Thread Brett @Google
On Fri, Mar 16, 2012 at 6:41 PM, Eric Covener wrote: >> I'm just saying the documentation of the new matching scheme is >> deceptive, not that any code should be changed.. > > Operative point I'm trying to make is that there should not be a new > matching scheme -- at best only new doc that didn't

Re: [users@httpd] apache 2.4 virtualhosts

2012-03-16 Thread Eric Covener
> I'm just saying the documentation of the new matching scheme is > deceptive, not that any code should be changed.. Operative point I'm trying to make is that there should not be a new matching scheme -- at best only new doc that didn't get backported since it also dropped _default_ and NameVirtu

Re: [users@httpd] apache 2.4 virtualhosts

2012-03-16 Thread Eric Covener
On Fri, Mar 16, 2012 at 4:08 AM, Brett @Google wrote: > > # This first-listed virtual host is also the default for *:80 > ServerName www.example.com > ServerAlias example.com *.example.com > DocumentRoot /www/domain > > > > ServerName other.example.com > DocumentRoot /www/otherdomain > > > Abo

Re: [users@httpd] apache 2.4 virtualhosts

2012-03-15 Thread Eric Covener
> I think so. This is a paradigm shift for people using NameVirtualHost > a.b.c.d and taking advantage of the old "default" per-ip container > for virtualhost patterns matching a.b.c.d. on the same port. The > wildcard in the first container is what is causing the problem for me. In 2.4, the only

Re: [users@httpd] apache 2.4 virtualhosts

2012-03-15 Thread Brett @Google
On Fri, Mar 16, 2012 at 12:38 AM, Eric Covener wrote: >> In your example it checks in the virtual hosts matching ip:port in >> config file order : >> >> 1. ServerName www.example.com >> >> 2. ServerName gone.example.com >> >> 3. ServerName forbidden.example.com >>    ServerAlias *.example.com >> >

Re: [users@httpd] apache 2.4 virtualhosts

2012-03-15 Thread Eric Covener
On Thu, Mar 15, 2012 at 10:24 AM, Brett @Google wrote: > Is order significant ? I think order is only significant in these cases: 1) the first-listed is the default if no name/alias match 2) if you have duplicate servername/servername or serveralias/serveralias [untested, presuming consistent re

Re: [users@httpd] apache 2.4 virtualhosts

2012-03-15 Thread Brett @Google
Is order significant ? In your example it checks in the virtual hosts matching ip:port in config file order : 1. ServerName www.example.com 2. ServerName gone.example.com 3. ServerName forbidden.example.com ServerAlias *.example.com The wildcard is last in your example, in mine it is first

Re: [users@httpd] apache 2.4 virtualhosts

2012-03-15 Thread Eric Covener
> If i comment out > "ServerAlias *.example.com" traffic to test.example.com goes to the > more specific container and others to the default, but only because > "revproxy.internal" is also the name of the server in the global > server configuration, so the first virtualhost also happens to be the >

Re: [users@httpd] apache 2.4 virtualhosts

2012-03-15 Thread Brett @Google
On Thu, Mar 15, 2012 at 7:37 PM, Tom Evans wrote: >> Ideally i'd like to do something like (whihc i could do in apache 2.2 >> - by virtue of NameVirtualHost, and grouping by IP with one as the >> default) : >> >> # serve a "we dont host this web site error message" by default for >> *.example.com

Re: [users@httpd] apache 2.4 virtualhosts

2012-03-15 Thread Tom Evans
On Thu, Mar 15, 2012 at 1:35 AM, Brett @Google wrote: > Hello, > > There is an example at : > http://httpd.apache.org/docs/2.4/vhosts/name-based.html > > > # This first-listed virtual host is also the default for *:80 > ServerName www.example.com > ServerAlias example.com *.example.com > Documen

[users@httpd] apache 2.4 virtualhosts

2012-03-14 Thread Brett @Google
Hello, There is an example at : http://httpd.apache.org/docs/2.4/vhosts/name-based.html # This first-listed virtual host is also the default for *:80 ServerName www.example.com ServerAlias example.com *.example.com DocumentRoot /www/domain ServerName other.example.com DocumentRoot /www/otherd