You can consider also
Order allow,deny
Deny from all
sections are processed in the order they appear in the configuration
file, after the sections and .htaccess files are read, but before
sections. Note that can be nested inside sections
to restrict the portion of the filesystem t
> I tried to do the deny *.inc but doing so just made it so the browser can't
> even include them. So that won't do the trick.
Uh, what? Aren't these .inc files included by PHP scripts? PHP has no
way of knowing whether you are denying access to them from the httpd.conf
level with a proper deny
I have about 20 virtual hosts on my server and all of them have shtml and
some php files that look to a directory /includes/ which is aliased (in the
srm.conf file) over to a main includes directory under the root dir.
Alias /includes/ /usr/local/etc/httpd/htdocs/includes/
If I change this alias
3 matches
Mail list logo
