Testing URL ReWrite .htaccess or web.config

There are at least two methods to test if URL ReWrite is functioning:

• Are pretty permalinks working?
• Break .htaccess or web.config to determine if the web server is processing URL ReWrite. Interestingly, IIS and Apache are subject to the same “break” and both respond with server errors if rewrite is broken.

IIS web.config

• Add some un-commented text, ie. outside of the well-formed xml tags

<?xml version="1.0" encoding="UTF-8"?>
<!-- comments -->
break rewrite
<configuration>

Apache .htaccess

• Add some un-commented text anywhere

# DOMAIN.TLD
# running as FastCGI so NO CAN USE php_value
# but 5.3 supports per dir php.ini
break rewrite

If the URL ReWrite file is broken, and if the web server, either IIS or Apache, is processing the web.config or .htaccess of interest, an HTTP error is emitted by the server. Depending on error handling configuration, you might see the web server’s default error page, or you might see a custom error page, or you may simple be redirected to the site’s home page (endless loop).