181 reputation
110
bio website blog.gahooa.com
location Altoona, PA
age
visits member for 5 years
seen Jul 8 at 15:44

Aug
4
revised Apache access restriction based on file and directory name
added 145 characters in body; added 313 characters in body
Aug
4
comment Apache access restriction based on file and directory name
Hey, that's really close. But it's running into the same problem I was having... /_sam/__foo__.txt is allowed. My wheels are turning, however, and I think this is the right approach. Maybe I should wait until morning :)
Aug
4
comment Apache access restriction based on file and directory name
Hi Craig. I believe your suggested rule order would allow /_hidden/__init__.php -- is that true? Regarding the BTW, I appreciate you taking the time to write that, but can assure you that there is a bigger picture that I did not take up room in the post to explain. 99% of our non-http accessible files are completely outside the DocumentRoot, but there are some specific exception (with very good cause) that live inside the document root. Either they are directory level PHP or Python runtime configuration files. Calling this silly would be the same as calling apache's .htaccess silly.
Aug
4
comment Apache access restriction based on file and directory name
As I pointed out in my post, I am using <Directory ~ "..."> which, according to the apache docs, are exactly the same as <DirectoryMatch ...>.
Aug
4
awarded  Student
Aug
3
awarded  Editor
Aug
3
revised Apache access restriction based on file and directory name
added 8 characters in body; edited tags
Aug
3
asked Apache access restriction based on file and directory name
Jul
4
awarded  Supporter