--On 30 May 2012 15:06:15 -0400 Eric Covener <covener@xxxxxxxxx> wrote:
Is there anything else I can do, like (e.g.) put the IP address as a hex constant or something in <VirtualHost>? Or disable this rather annoying feature?I'd suggest opening a bug report that something weird seems to happen with the literal IP address in the <virtualHost arguments and that it works with *:80.
OK, that gives me an idea. My config looks a bit like this: # Listen on 192.200.0.1, 192.200.0.2, 192.200.0.3 Listen *:80 Listen *:1234 # <--- config for this not omitted below NameVirtualHost 192.200.0.1:80 <VirtualHost 192.200.0.1:80> # <--- *** THIS LINE *** ServerName will-not-resolve.example.com:80 # port no included as per docs # Default vhost for things that resolve to 192.200.0.1 </VirtualHost> <VirtualHost 192.200.0.1:80> ServerName a.web.site.example.com:80 # port no included as per docs # VHost for http://a.web.site.example.com/ </VirtualHost> <VirtualHost 192.200.0.1:80> ServerName 192.200.0.1:80 # port no included as per docs # VHost for http://192.200.0.1/ </VirtualHost> # 192.200.0.2 <VirtualHost 192.200.0.2:80> # IP based Virtual Host goes here on 192.200.0.2 </VirtualHost> To recap the problem is that accessing http://192.200.0.1/ returns the default site (the first one), not the specific site (the third). Suppose I change the line marked '*** THIS LINE ***" so it reads <VirtualHost *:80> # <--- *** THIS LINE *** Will that interfere in any way with the IP based virtual host which is the fourth above? I have no other name based virtual hosts and even if I did, I wouldn't mind this being the global default. And will it fix the issue that http://192.200.0.1/ is not connecting to the third virtual host block above? -- Alex Bligh --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|