On 6/26/06, Matus UHLAR - fantomas <[EMAIL PROTECTED]> wrote:
Hello,
this is my current configuration of apache (debian: 1.3.33-6sarge1):
NameVirtualHost 195.168.3.66:80
<VirtualHost 195.168.3.66:80>
ServerName default.fantomas.sk
DocumentRoot /home/webs/default.fantomas.sk
</VirtualHost>
<VirtualHost 195.168.3.66:80>
ServerName fantomas.fantomas.sk
DocumentRoot /home/webs/fantomas.fantomas.sk
</VirtualHost>
<VirtualHost 195.168.3.66:80>
ServerName 195.168.3.66
DocumentRoot /home/webs/195.168.3.66
</VirtualHost>
However, with this configuration I was not able to reach virtual host
195.168.3.66. It seems that apache accepts name defined in
<VirtualHost [NAME]> as one of hames for name virtual host -
when I switched to <VirtualHost fantomas.fantomas.sk>, I couldn't reach
virtual host for fantomas.fantomas.sk.
I can not simply use <VirtualHost *> because of different virtual servers
running at different IP addresses. Also, at other sites I'm configuring
apache from databases that contain server-IP pairs, configuring given server
at given IP, and exporting this configuration to DNS.
Can anyone confirm this behaviour? Can anyone explain to my, why was
name-based virtual hosting made this way?
I'm fairly sure you are incorrect in your interpretation, although
there is no way I'm going to load up a 1.3 server to test with.
To see what is really going on, add %{Host}o and %v to your LogFormat
to see what apache is seeing and how it is interpreting it.
Joshua.
---------------------------------------------------------------------
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: [EMAIL PROTECTED]
" from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
