Matus UHLAR - fantomas wrote: >> Your problem here is that the ServerName requires a fully-qualified >> domain name, rather than an IP address. > > I think that ServerName could contain anything that users may request in the > Host: header ;-) Yes, I'd gathered that you think it ought to do something other than what it does do. > The documentation (somehow) says that virtual host applies, if the requested > name matches ServerName or ServerAlias. What I show here is, that it matches > even if the requested name matches the "name" defined in > <VirtualHost "name"> which is not documented (and causes problems to me). The documentation says: "ServerName fully-qualified-domain-name[:port]" so you might be falling at the first hurdle, because you're not specifying a FQDN. Also: "If no ServerName is specified, then the server attempts to deduce the hostname by performing a reverse lookup on the IP address. If no port is specified in the ServerName, then the server will use the port from the incoming request. For optimal reliability and predictability, you should specify an explicit hostname and port using the ServerName directive." So in your case it may actually be resolving fantomas.fantomas.sk, if it's deciding that the IP doesn't count as a ServerName. This may, however, be completely irrelevant. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|