Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
litespeed_wiki:rewrite_logs [2013/08/13 19:41]
Michael
litespeed_wiki:rewrite_logs [2013/08/13 19:48]
Michael [For Installations Using Apache Configuration Files]
Line 1: Line 1:
 ====== Enabling Rewrite Logs ====== ====== Enabling Rewrite Logs ======
  
-The first step to debugging rewrite rules is to enable rewrite logging. Once rewrite logging has been enabled, you will be able to see rewrite ​errors in your virtual host's error log (or your main error log if the virtual host uses the main error log). These log entries ​will tell you which rewrite rule is not working and what is going wrong.+The first step to debugging rewrite rules is to enable rewrite logging. Once rewrite logging has been enabled, you will be able to see rewrite log entries ​telling ​you which rewrite rule is not working and what is going wrong.
  
 This wiki will guide you through the steps to enabling rewrite logging both for native LiteSpeed Web Server installations and installations running off Apache configuration files. This wiki will guide you through the steps to enabling rewrite logging both for native LiteSpeed Web Server installations and installations running off Apache configuration files.
Line 7: Line 7:
 ====== For Native LSWS Installations ====== ====== For Native LSWS Installations ======
  
-Enabling rewrite logging in the WebAdmin console is very simple. First, ​you need to locate the virtual host that is having the problem. Then you just raise Log Level in your Rewrite settings above ''​0''​. Before that, though, you should check the vhost'​s log level. Rewrite log entries will go in the virtual host's main log, so make sure the virtual host's Log Level setting is set to ''​INFO''​ or ''​DEBUG''​. ​(WebAdmin console > Configuration > Virtual Hosts > Log) (Rewrite log entries are considered info level.)+Enabling rewrite logging in the WebAdmin console is very simple. First, locate the virtual host that is having the problem. Rewrite log entries will go in the virtual host's main log, so make sure the virtual host's Log Level setting ​(WebAdmin console > Configuration > Virtual Hosts > Log) is set to ''​INFO''​ or ''​DEBUG''​. (Rewrite log entries are considered info level.)
  
 {{vhost_log_level.png?​700}} {{vhost_log_level.png?​700}}
Line 19: Line 19:
 {{rewrite_log_level.png?​700}} {{rewrite_log_level.png?​700}}
  
-Graceful restart so the changes will take affect.+Graceful restart so the changes will take effect.
  
 ====== For Installations Using Apache Configuration Files ====== ====== For Installations Using Apache Configuration Files ======
Line 25: Line 25:
 If your installation of LSWS is using Apache'​s configuration files, you will need to enable rewrite logging in your Apache configurations. If your installation of LSWS is using Apache'​s configuration files, you will need to enable rewrite logging in your Apache configurations.
  
-In order to enable rewrite logging, you will first need to locate the virtual host where the error is occurring. If you are using cPanel, everything is usually in your ''​httpd.conf''​ file. Other setups may have virtual hosts in separate directories.+First, you will need to designate a file for the rewrite log. This is done at the server level (in Apache'​s ''​httpd.conf''​ file) with the RewriteLog directive. For example: 
 + 
 +  RewriteLog "/​usr/​local/​var/​apache/​logs/​rewrite.log"​ 
 + 
 +You need to locate the virtual host where the error is occurring ​so you can set the rewrite log level for that virtual host. If you are using cPanel, everything is usually in your ''​httpd.conf''​ file. Other setups may have virtual hosts in separate directories.
  
 In your virtual host settings, add the RewriteLogLevel directive followed by a number for how detailed you want your logs to be. ''​1''​ is least detailed. ''​9''​ is most detailed. ''​0''​ will turn off rewrite logging. For example: In your virtual host settings, add the RewriteLogLevel directive followed by a number for how detailed you want your logs to be. ''​1''​ is least detailed. ''​9''​ is most detailed. ''​0''​ will turn off rewrite logging. For example:
Line 31: Line 35:
   RewriteLogLevel 2   RewriteLogLevel 2
  
-You will also need to designate a file for the rewrite log. This is done at the server level with the RewriteLog directive. For example: +Graceful restart LSWS so the changes ​will take effect.
- +
-  RewriteLog "/​usr/​local/​var/​apache/​logs/​rewrite.log"+
  
 More information on Apache rewrite log configuration can be found in [[http://​httpd.apache.org/​docs/​2.2/​mod/​mod_rewrite.html|the Apache mod_rewrite documentation]]. More information on Apache rewrite log configuration can be found in [[http://​httpd.apache.org/​docs/​2.2/​mod/​mod_rewrite.html|the Apache mod_rewrite documentation]].