We have recognized an issue where IP deny code in the .htaccess will stop working:
order deny,allow
deny from all
allow from 12.34.96.342
This will not stop the pages from loading in your sub directories if you have the Frontpage .htaccess rules as follow:
deny from all
allow from 12.34.96.342
# -FrontPage-
IndexIgnore .htaccess */.??* *~ *# */HEADER* */README* */_vti*
<Limit GET POST>
order deny,allow
deny from all
allow from all
</Limit>
<Limit PUT DELETE>
order deny,allow
deny from all
</Limit>
AuthName domain.com
AuthUserFile /home/username/public_html/_vti_pvt/service.pwd
AuthGroupFile /home/username/public_html/_vti_pvt/service.grp
IndexIgnore .htaccess */.??* *~ *# */HEADER* */README* */_vti*
<Limit GET POST>
order deny,allow
deny from all
allow from all
</Limit>
<Limit PUT DELETE>
order deny,allow
deny from all
</Limit>
AuthName domain.com
AuthUserFile /home/username/public_html/_vti_pvt/service.pwd
AuthGroupFile /home/username/public_html/_vti_pvt/service.grp
This will override a lock from the parent directory. So, if you are locking content from home/username/.htaccess , then please make sure a child .htaccess is not overriding your locks.