On 05/14/2011 01:13 AM, David Mehler wrote:
Hello,
Thank you for your reply. From what your telling me the below is
wrong. Is the only correction I have to make the elimination of the
duplicate<Directory /> sections in the virtual hosts or do I have to
take out more?
An SSL NameVirtualHost will only function under specific circumstances.
Odds are you don't meet or need these.
Other than that, yes, that's all.
Thanks.
Dave.
# httpd.conf
# location of the web server tree
DocumentRoot "/var/www/html"
# Configure Directory Security
<Directory />
Order Deny,Allow
Deny from all
Options None
AllowOverride None
</Directory>
<Directory /var/www/html>
Order Allow,Deny
Allow from all
</Directory>
# Set up Name Virtual Hosts on the default http and https ports
NameVirtualHost *:80
NameVirtualHost *:443
# vhost.conf
#
# Virtual host file
#
# The default (Catch all) Virtual host.
<VirtualHost *:80>
ServerName default
DocumentRoot /var/www/html
ErrorDocument 404 /index.html
<Directory />
Order Deny,Allow
Deny from all
Options none
AllowOverRide none
</Directory>
<Directory /var/www/html>
Order Allow,Deny
Allow from all
Options none
AllowOverRide none
</Directory>
</VirtualHost>
# The example.com http virtual host
<VirtualHost *:80>
ServerAdmin [email protected]
ServerName example.com
ServerAlias www.example.com
DocumentRoot /srv/www/example.com/public_html
ErrorLog /srv/www/example.com/logs/error_log
CustomLog /srv/www/example.com/logs/access_log common
<Directory />
Order Deny,Allow
Deny from all
Options none
AllowOverRide none
</Directory>
<Directory /srv/www/example.com/public_html>
Order Allow,Deny
Allow from all
Options none
AllowOverRide none
</Directory>
</VirtualHost>
On 5/13/11, Jeroen Geilman<[email protected]> wrote:
On 05/13/2011 06:50 AM, David Mehler wrote:
Hello,
I've got a question on virtual hosts. I'm running httpd 2.2.3 on a
rhel5 machine. I believe from what I've read that when one sets up a
virtual host that the Listen and other directives in httpd.conf are no
longer valid.
Listen may only be used in the server context. It is invalid in a
virtualhost context.
FIrst of all, did I get that right? I've got a Listen
line in httpd.conf telling apache to listen to a single address,
Listen tells apache what PORT to listen on, first of all.
If your distro did not pre-set this (they did), set it to Listen 80 for
normal HTTP.
You may repeat it as often as required, for SSL (443), or per-IP
(127.0.0.1:80) or any combination thereof.
I've
also got a
<Directory />
Order Deny,Allow
Deny from all
Options none
AllowOverRide none
</Directory>
in that file as well as a block pointing to apache's document root
area. In my virtual host configuration file I've got the virtual host
set up with a different document root area, my question is is the
<Directory /> block from the httpd.conf file still propagated to the
virtual host configuration file or do I have to define that<Directory
/> block in the virtual hosts as well? I hope that made sense.
No, do not repeat Directory /.
Yes, all settings that can be inherited, are inherited.
Thanks.
Dave.
Where is the conceptual question ?
--
J.
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
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]
--
J.
---------------------------------------------------------------------
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]
