Understanding Invalid Rewrite Directive Logs in OpenLiteSpeed

If you're using OpenLiteSpeed, you might notice log messages like the following:

2024-03-12 10:17:43.112478 [INFO] [512734] RewriteFile [/var/www/uuid/public_html/wp-content/uploads/.htaccess] parsed, return 0.
2024-03-12 10:17:55.389201 [INFO] [512735] Invalid rewrite directive: <Files *.php>
2024-03-12 10:17:55.389278 [INFO] [512735] Invalid rewrite directive: Deny from all
2024-03-12 10:17:55.389302 [INFO] [512735] Invalid rewrite directive: </Files>

These are normal informational logs. cPFence adds standard Apache-style access rules for added protection. OpenLiteSpeed may log them as "invalid", but there is no impact on security or functionality.

OpenLiteSpeed only supports basic .htaccess rules such as simple rewrites. More advanced directives like <Files> blocks are not supported and are simply ignored.

These rules continue to work properly on Apache and LiteSpeed Enterprise. On OpenLiteSpeed, it's safe to ignore these messages—they do not affect your website or cPFence protection.

No action is needed. Everything is working as expected.


Need Further Assistance?

If you encounter any issues or need additional help, feel free to reach out to

  • 0 Uživatelům pomohlo
Byla tato odpověď nápomocná?

Související články

Why my custom WAF rules are not working?

If your custom ModSecurity rules aren’t taking effect, it’s often due to duplicate rule IDs or...

How to Block or Whitelist Certain User Agents ?

This guide will help you block or whitelist specific user agents in cPFence. You can manage these...

How to Enable / Disable WAF Rule by ID ?

This guide provides instructions for enabling and disabling specific WAF (Web Application...

How to Enable / Disable WAF?

The cPFence Web Application Firewall (WAF) now fully supports Apache, Nginx, OLS, and LSWS web...

How to Identify Problematic WAF Rule IDs in cPFence?

New! You can now use an automatic tracking tool to identify problematic WAF rules in real time....