====== My rewrite rules not working, is it a LiteSpeed bug? ======
 
Make sure the rewriting engine has been enabled:
<code>
RewriteEngine On
</code>

Place the following in related Directory Directive in the httpd.conf to enable .htaccess override.
<code>
AllowOverride All
</code>

Enable the rewrite log if you have such privileges. Set RewriteLog path and RewriteLogLevel. 

For Apache vhost, add the following to httpd.conf. ([[http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html#rewriteloglevel|Apache 2.2 reference RewriteLogLevel Directive]])
<code>
RewriteLogLevel 2 #(up to 9)
</code>

It has been replaced by the following new per-module logging configuration mentioned in 2.4 version:([[http://httpd.apache.org/docs/current/mod/mod_rewrite.html|Apache 2.4 reference]])
<code>
LogLevel alert rewrite:trace3 #( up to trace8 log levels)
</code>
To get just the mod_rewrite-specific log messages, pipe the log file through grep:
<code>
tail -f error_log|fgrep '[rewrite:'
</code>
For LSWS native vhost, LSWS web admin -> Virtual Host -> vhost abc -> Rewrite -> Log Level:9

Then check the log for errors.

For WHM/cPanel, it's usually located at /usr/local/apache/logs/error_log.

For LSWS native server or vhosts, the error log file paths are configured in LSWS web admin -> Server or Virtual Hosts -> Log.

Sometime you may be wondering why it was working with Apache before but now seems not working with LiteSpeed. Is that true? Try to switch to Apache to test your rule to make sure it is really working before you log a bug with LiteSpeed. Quite often, it doesn't work with Apache either and rule sets need to be reordered or modified.