An easy way to test your RewriteRules
Makes debugging Apache mod_rewrite rules easier
This tool lets you write and test your rewrite rules for Apache's mod_rewrite on-the-fly.
If you'd like to learn more about mod_rewrite, I recommend The Definitive Guide to Apache mod_rewrite
Apache Docs for RewriteRule · Apache mod_rewrite guide
Notice a problem?
I'm still working on this tool and would appreciate if you let me know if you had a problem with your testing. Please enter your email and a short note about what problem you're having below and hit Send, which will send me your ruleset and a debug log of your session here.
Rules are saved in a session, so they are deleted after ~30 minutes of inactivity. Don't get distracted.
What works?
- RewriteRule statements with backreferences. The patterns are implemented as full POSIX-compliant regular expressions; I still need to work out any inconsistencies with mod_rewrite's parser.
- The RewriteRule flags that make sense/have an effect on the parsing in this tool. Currently C (chain), S (skip), L (last), NC (nocase), QSA (qsappend) and N (next) are supported.
- RewriteCond variables, i.e. %{REMOTE_HOST}, and the two flags that RewriteCond supports: NC (nocase) and OR (ornext). Note that the tool does not check that you're using valid variable names.
- RewriteCond backreferences, both RewriteCond and RewriteRule. %1 refers to the first subpattern of the last RewriteCond in this group, $0 refers to the first subpattern of the RewriteRule that the current RewriteCond applies to. Yes, one is 0-indexed and the other is not.
What doesn't work?
- RewriteMaps aren't supported because of the amount of work needed to implement it here and the ease with which one can test them already.
- RewriteBase isn't supported because it doesn't really make sense here.
- The other mod_rewrite options aren't interesting in this context either.
This site requires Javascript to be enabled.
Pretty soon there'll be something exciting here: Time To Reply, for people providing email support.
