On Wed, May 30, 2012 at 3:06 PM, 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.
On 30.05.12 22:10, Eric Covener wrote:
Sorry, just catching on now that Matus nailed it. It's not so clear what the code is trying to tolerate by comparing this way.
I guess that this was historic workaround for defining name-based virtual servers without defining ServerName/ServerAlias
<VirtualHost one.na.me> # one.na.me served here </VirtualHost> <VirtualHost another.na.me> # another.na.me </VirtualHost>Since this makes creating default-only name-based virtual hosts impossible, I've had to found the workaround mentioned in my previous mail.
I've been trying to solve this problem in the past, but I was only directed to the mentioned docs, I remember no explanation of why this is done.
-- Matus UHLAR - fantomas, uhlar@xxxxxxxxxxx ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Micro$oft random number generator: 0, 0, 0, 4.33e+67, 0, 0, 0... --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|