Here you may find step-by-step instruction on how to troubleshoot your ISAPI_Rewrite
- First of all to correctly troubleshoot your problem we require you to run
the latest build of ISAPI_Rewrite available. You can always upgrade your ISAPI_Rewrite
3 installation by downloading current build from our web site here http://www.helicontech.com/download-isapi_rewrite3.htm
- Most of the problems with running ISAPI_Rewrite lay in NTFS permissions
restrictions configured on your server. So please read Permissions
required to run ISAPI_Rewrite document first.
- Please check Application and System logs for error messages. This may point
you to the error source.
- Don't forget to put RewriteEngine on directive in every configuration
file you are using.
- Put the following lines into httpd.conf file:
This will create error.log and rewrite.log
files by default in the installation directory. If log files are created,
this will indicate that ISAPI_Rewrite is running. Read resulting error.log
and rewrite.log files, this may give you some clue on a problem source.
- If httpd.conf rules are working but no .htaccess files are loaded, please
check NTFS permissions on .htaccess files again and make sure you are not
using Lite version of ISAPI_Rewrite.
- If rules are working in httpd.conf file but not in other sections or .htaccess
files, make sure to include RewriteEngine on directive in every section
and .htaccess file. Also remember that rewriting base inside .htaccess files
by default is different from httpd.conf. ISAPI_Rewrite automatically strips
the local directory prefix from the path when in .htaccess or <Directory>
section and applies rules only to the remainder. So if your rules start with
a '/' character, this should be removed in .htaccess file in the root folder
of web site.
If you still having problems with using ISAPI_Rewrite, please write your question
on the Support forum or send
it to the Support e-mail.
Please include the following information in your support request:
- Your ISAPI_Rewrite configuration file, including path and file names.
- A link to your web site.
- URL that you have used for testing your rules
- Copy of error.log and rewrite.log files with failed requests.
- Portion of IIS log file that include failed requests.
Remember the more information you provide the easier it will be for us to
resolve your problem, thus you will have more chances to get fast resolution.