httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tom Frost <fro5...@yahoo.com>
Subject Re: [users@httpd] VirtualHost configuration not working as expected with ePages solution
Date Mon, 07 Jan 2013 15:02:44 GMT
Hi

Thanks for your reply Adam.

The output requested is:

VirtualHost configuration:
127.0.0.1:443          localhost (/etc/httpd/conf.d/ssl.conf:81)
wildcard NameVirtualHosts and _default_ servers:
*:80                   is a NameVirtualHost
         default server url2.mydomain.com (/etc/httpd/conf.d/zzz-epages-httpd.conf:215)
         port 80 namevhost url2.mydomain.com (/etc/httpd/conf.d/zzz-epages-httpd.conf:215)
         port 80 namevhost url2.mydomain.com (/etc/httpd/conf.d/zzz-epages-httpd.conf:225)
         port 80 namevhost url2.mydomain.com (/etc/httpd/conf.d/zzz-epages-httpd.conf:215)
         port 80 namevhost url2.mydomain.com (/etc/httpd/conf.d/zzz-epages-httpd.conf:225)
Syntax OK

As for the DNS query, I'm pretty sure this is right, I have added Host (A) entries in DNS
for both url1 and url2.

Any thoughts to the apachectl output? I am not actually using the _default_ anymore, just
both *:80.

Thanks again,
Tom


________________________________
 From: Adam Dosch <adam@wisehippy.com>
To: Tom Frost <fro5tie@yahoo.com>; users@httpd.apache.org 
Sent: Thursday, 3 January 2013, 19:28
Subject: Re: [users@httpd] VirtualHost configuration not working as expected with ePages solution
 
Tom,

I'd be curious what the output of your 'apachectl -t -D DUMP_VHOSTS' looks like?

I've come across this problem as well in a related degree, and interrogating the output of
the 'DUMP_VHOSTS' above will at least tell you the top-to-bottom order your vhost requests
will travel down in your configuration.

One way I had to solve it was take my VirtualHost container for '_default_', put it in it's
own configuration file and include it prior to any other vhost config files in httpd.conf. 
It looked a bit like this in my httpd.conf:

  NameVirtualHost *:80
  Include conf/mydefault-vhost.conf # which would contain your default vhost container for
url2.mydomain.com
  Include conf/*-vhost.conf # contain your others like url1, urlfoo, urlboo, urlbar, etc.,
it would be one config, or many, your choice.

Using this approach, I did notice that a blanket wildcard/greedy include of all *.conf file
gives you varying results, especially if you were managing all your vhosts in separate configuration
files for clarity/organization sake like I was.

Otherwise, sounds like you've verified client-side caching.  My last logical thought would
be perhaps if you're not using CNAME's in DNS for this and right-out calling them from the
client without any hostname resolution on those FQDNs, that you need to add that those host
aliases of 'url1.mydomain.com' and 'url1.mydomain.com' to your /etc/hosts or equiv in Windows.

-A

On Thu, 3 Jan 2013 08:05:26 -0800 (PST), Tom Frost wrote:
> If I use either url1.mydomain.com or url2.mydomain.com they both go
> to the url2.mydomain.com VirtualHost site.
> 
> I have cleared caches and done a Ctrl-F5 to force the page to reload. 
> 
> I'm sure that its something to do with epages, as I said there is a
> lot of other config in there but I'm honestly not sure what is what.
> 
> Thanks again for your help, any more suggestions would be appreciated.
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Mime
View raw message