DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13411>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13411
Named virtual hosts on different ports, different content
Summary: Named virtual hosts on different ports, different
content
Product: Apache httpd-2.0
Version: HEAD
Platform: Other
URL: http://localhost/manual/vhosts/examples.html
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Documentation
AssignedTo: bugs@httpd.apache.org
ReportedBy: apang@mdsi.ca
It reads:
"The above configuration is what you will want to use in almost all
name-based virtual hosting situations. The only think that this configuration
will not work for, in fact, is when you are serving different content based on
differing IP addresses or ports."
Typo: "think" should be changed to "thing".
Also, to fill the gap identified in the above, please add an example of serving
different content from different ports. For example, the configuration snippet
below, serves different content between http://www.example.com/ and
https://www.example.com/.
In httpd.conf:
NameVirtualHost *:80
<VirtualHost *:80>
ServerName www.example.com
DocumentRoot /var/www/html/example
<Directory /var/www/html/example>
Options Includes
</Directory>
</VirtualHost>
<VirtualHost *:80>
ServerName www.test.com
DocumentRoot /var/www/html/test
<Directory /var/www/html/test>
Options Includes
</Directory>
</VirtualHost>
In ssl.conf:
NameVirtualHost *:443
<VirtualHost *:443>
ServerName www.example.com
DocumentRoot /var/www/html/secure
<Directory /var/www/html/secure>
AllowOverride AuthConfig
</Directory>
</VirtualHost>
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
|