@drazon
404 Detection depends on permalinks enabled …
So the 404 File/folder whitelist probably does not work with wildcards.
dwinden
Thread Starter
drazon
(@drazon)
Thank you for your answer but I’m not sure I follow, I have the permalinks as domain.com/postname so what’s next?
@drazon
Adding /wp-content/uploads/ (folder) to the 404 whitelist will not prevent
/wp-content/uploads/file1.jpg
/wp-content/uploads/file2.jpg
/wp-content/uploads/…….
from being logged as a 404.
You will need to add:
/wp-content/uploads/file1.jpg
/wp-content/uploads/file2.jpg
to the 404 whitelist for these 404 requests to be whitelisted.
dwinden
@drazon
If you require no further assistance please mark this topic as ‘resolved’.
dwinden
Thread Starter
drazon
(@drazon)
I appreciate your answer but the thread can not be marked as resolved since there is no solution to whitelist all files in a folder. I have a plugin that auto generates several files inside /wp-content/cache/standard-hashfilerandom.js , or /wp-content/cache/standard-hashfilerandom.css
The only common word in the filename is “standard”
Google and other safe bots visit the old cache files and get locked out.
@drazon
Ok, I see.
I think the issue here is that because you can specify a folder for 404 Whitelist people think that all files in that folder will then not trigger a 404 log entry and not be counted towards a lockout.
However it seems to me this is not how it is designed to work.
As to your wp-content/cache/standard*.js and standard*.css example I think the .css will generate a 404 entry in the log but it will not be counted towards a lockout.
The same will happen to *.js files if you add such entry to the 404 Ignored Filetypes setting.
If you really need 404 whitelisted folders to work differently the best thing to do would be to submit a feature request here.
dwinden
Thread Starter
drazon
(@drazon)
Thank you for your answer!
