Hey,
I'm trying to set up a web server on CentOS 4.4. I've got apache configured and my content in the root of the webdir (/var/www/html/). This works fine.
I've then tried to add in webalizer to the mix, so I can view my site stats. I've placed the usage directory (containing the webalizer pages) into /var/www/html/usage/). I want to lock down that to my LAN IP address, so in /etc/httpd/conf/httpd.conf I have;
<Directory "/var/www/html/usage">
Options None
AllowOverride None (I dont want to use .htaccess files particularly)
Order Deny,Allow
Deny from All
Allow from 192.168.0.2
</Directory>
Save and reload apache. I then try to access that page from my LAN machine and I get 403 error. If I SSH onto the webserver and load up a browser, then type in;
http://my_server_ip/usage/index.html
I get the same problem. If I use;
http://localhost/usage/index.html
It works! ?!?!
I've set Apache to listen on eth0's IP, and normal content in the root web directory works ok
Any ideas please? am I missing something very simple? I didn't have this problem on my old SuSE server.
I'm placing this directory statement directly below the statement for the root web directory.
I'm trying to set up a web server on CentOS 4.4. I've got apache configured and my content in the root of the webdir (/var/www/html/). This works fine.
I've then tried to add in webalizer to the mix, so I can view my site stats. I've placed the usage directory (containing the webalizer pages) into /var/www/html/usage/). I want to lock down that to my LAN IP address, so in /etc/httpd/conf/httpd.conf I have;
<Directory "/var/www/html/usage">
Options None
AllowOverride None (I dont want to use .htaccess files particularly)
Order Deny,Allow
Deny from All
Allow from 192.168.0.2
</Directory>
Save and reload apache. I then try to access that page from my LAN machine and I get 403 error. If I SSH onto the webserver and load up a browser, then type in;
http://my_server_ip/usage/index.html
I get the same problem. If I use;
http://localhost/usage/index.html
It works! ?!?!
I've set Apache to listen on eth0's IP, and normal content in the root web directory works ok

Any ideas please? am I missing something very simple? I didn't have this problem on my old SuSE server.
I'm placing this directory statement directly below the statement for the root web directory.