Re: [users@httpd] VirtualHost configuration not working as expected with ePages solution
On Thu, 10 Jan 2013 17:15:48 +, Tom Evans wrote: On Thu, Jan 10, 2013 at 12:03 PM, Tom Frost fro5...@yahoo.com wrote: Hi Adam Thanks for your reply. Yes, I did c/p and then replace the domains with the placeholders. I too noticed that there wasnt any entry for url1.mydomain.com, and I have been down the same process you advised of starting with one working and gradually adding. So I start off with httpd.conf and the relevant lines are: NameVirtualHost *:80 Include conf.d/*.conf IfDefine PROXY Is this so that this vhost is only loaded in the case that the proxy module is included in Apache? If so, I would completely drop it. If the proxy_module is not available, your website would not work anyway, and better to be told that when starting apache, than apache to silently drop your vhost and start up anyway. If you did want to keep it (and I correctly guessed why it is there), you should replace it with this: IfModule proxy_module I would just drop it though. With this gone, httpd should see the url1.domain.com vhost as the first and default vhost, and all should work. Please test. Tom F, thanks for posting it all. I was too lazy to go look back through the list to find the original postings of your config. I agree with Tom E., dump that IfDefine PROXY. The chances you aren't going to not load the proxy module some given time I'd say are slim; you're setting it up for a reason, so it's needed. Instead of making your configuration 'that' dynamic, if you decide not to use that vhost for url1 or don't use mod_proxy* for what you're doing, just remove it and quick change the vhost config. Keep it simple. -A - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] VirtualHost configuration not working as expected with ePages solution
Tom, Sorry for the belated reply. 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 I'm assuming you copy/pasted this out and replaced the real domains to 'protect the innocent'. But if you didn't flub copy/paste, I --do not-- see any indication that Apache knows what to do or will do anything specific when a request comes in for 'url1.mydomain.com'. If you notice the output above, you will always default to 'url2.mydomain.com' for any HTTP request coming in on that listening service on that IP address. There isn't --any-- VirtualHost reference to 'url1' listed. I forgot what your VirtualHost containers looked like for both ur1 and ur2 domains, but I think you definitely just take a isolation approach to it: work with one, get it working with it's own VirtualHost container, then add another vhost in and so on, then re-verify with 'apachectl -t -D DUMP_VHOSTS' and from a web browser. From there once you get it nailed down, then do any merging for maintenance sake on your .conf files. Hope that helps. -A - FROM: Adam Dosch TO: Tom Frost ; 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-unsubscr...@httpd.apache.org [1] For additional commands, e-mail: users-h...@httpd.apache.org [2] Links: -- [1] mailto:users-unsubscr...@httpd.apache.org [2] mailto:users-h...@httpd.apache.org - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
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-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
