Tips for debugging .htaccess rewrite rules

Many posters have problems debugging their RewriteRule and RewriteCond statements within their .htaccess files. Most of these are using a shared hosting service and therefore don't have access to the root server configuration. They cannot avoid using .htaccess files for rewriting and cannot enable a RewriteLogLevel" as many respondents suggest. Also there are amy .htaccess -specific pitfalls and constraints are aren't covered well. Setting up a local test LAMP stack involves too much of a learning curve for most.

So my Q here is how would we recommend that they debug their rules themselves . I provide a few suggestions below. Other suggestions would be appreciated.

1. 
   

   
   Understand that the mod_rewrite engine cycles through .htaccess files . The engine runs this loop:
   

   
   

   
   
   
   do
   
     execute server and vhost rewrites (in the Apache Virtual Host Config)
   
     find the lowest "Per Dir" .htaccess file on the file path with rewrites enabled
   
     if found(.htaccess)
   
        execute .htaccess rewrites (in the user's directory)
   
   while rewrite occurred
   
   
   
   

   
   

   
   So your rules will get executed repeatedly and if you change the URI path then it may end up executing other .htacess files if they exist. So make sure that you terminate this loop, if necessary by adding extra RewriteCond to stop rules firing. Also delete any lower level .htaccess rewrite rulesets unless explicitly intent to use multi-level rulesets.
   

   
   


2. 
   

   
   Make sure that the syntax of each Regexp is correct by testing against a set of test patterns to make sure that is a valid syntax and does what you intend with a fully range of test URIs. See answer below for more details.
   

   
   


3. 
   

   
   Build up your rules incrementally in a test directory. You can make use of the "execute the deepest .htaccess file on the path feature" to set up a separate test directory (tree) and debug rulesets here without screwing up your main rules and stopping your site working. You have to add them one at a time because this is the only way to localise failures to individual rules.
   

   
   


4. 
   

   
   Use a dummy script stub to dump out server and environment variables . (See Listing 2 )If your app uses, say, blog/index.php then you can copy this into test/blog/index.php and use it to test out your blog rules in the test subdirectory. You can also use environment variables to make sure that the rewrite engine in interpreting substitution strings correctly, e.g.
   

   
   

   
   
   
   RewriteRule ^(.*) - [E=TEST0:%{DOCUMENT_ROOT}/blog/html_cache/$1.html]
   
   
   
   

   
   

   
   and look for these REDIRECT_* variables in the phpinfo dump. BTW, I used this one and discovered on my site that I had to use %{ENV:DOCUMENT_ROOT_REAL} instead. In the case of redirector looping REDIRECT_REDIRECT_* variables list the previous pass. Etc..
   

   
   


5. 
   

   
   Make sure that you don't get bitten by your browser caching incorrect 301 redirects . See answer below . My thanks to Ulrich Palha for this.
   

   
   


6. 
   

   
   The rewrite engine seems sensitive to cascaded rules within an .htaccess context, (that is where a RewriteRule results in a substitution and this falls though to further rules), as I found bugs with internal sub-requests (1) , and incorrect PATH_INFO processing which can often be prevents by use of the [NS], [L] and [PT] flags.
   

   
   

Any more comment or suggestions?

Listing 1 -- phpinfo

<?php phpinfo(INFO_ENVIRONMENT|INFO_VARIABLES);

Source: Tips4all