autoprotect <Files> protects the entire directory

Hi !
I think the autoprotect.sh is not handling <Files xxxx> properly:

One of the plugins I use recently added a .htaccess which protects one file with <Flies> option:

Code:

cat /home/nginx/domains/hejazultra.org/public/wp-content/.htaccess
<Files debug_xxxxxxx.log>
            Order Allow,Deny
            Deny from all
        </Files>

running

Code:

/usr/local/src/centminmod/tools/autoprotect.sh

adds the following lines:

Code:

# /home/nginx/domains/hejazultra.org/public/wp-content
location ~* ^/wp-content/ { allow 127.0.0.1; deny all; }

( I confirmed by removing the .htaccess and re-running autoprotect.sh . the 2 lines disappear.)

---

something is off

 

Thanks for the quick answer, as always...

Well noted that Autoprotect currently works only on Directories and not on Files.
it would be tempting to say "maybe it should...", but since I am not the once coding it, I will refrain from doing that , as I do not know how complex it would be to do that (especially that there are both a https://httpd.apache.org/docs/2.4/mod/core.html#files & the regexp cousin https://httpd.apache.org/docs/2.4/mod/core.html#filesmatch) and I assume it is not much in use, otherwise others would have asked this feature before.

Perhaps I can make another suggestion though: It seems others have been bitten by the autoprotect feature before me. Until my site stopped working suddenly (*), I wasn't aware of the feature. It is a great feature. It is a must-have feature even now that I know about it, it makes perfect sense to have it. and it is a great differentiator from other hosting frameworks. Yes, it is better to have the site stopped working properly than the site hacked. But it would be great to be notified when a change happens.
I see autoprotects runs regularly and is detecting if there is a DIFF in the protection.
so when a new .htaccess is detected or a diff from previous version is detected, it would be a good time to notify the server/site owner by an email. ( not dissimilar to the cron'ed emails generated with wp-updater-domain.sh )
Thoughts?