Is there any way to debug redirection rules in.htaccess?

Is there any way to debug redirection rules in.htaccess? - If a page has internal and external outgoing links to redirecting URLs, it’s returning 3xx (301, 302, etc.) HTTP status codes standing for redirection. This issue means that the page does not exist on a permanent or temporary basis. It appears on most of the popular web browsers, usually caused by a misconfigured website. However, there are some steps you can take to ensure the issue isn’t on your side. You can find more details about redirecting URLs by reading the Google Search Central overview. In this article, we’ll go over how you can fix the Is there any way to debug redirection rules in.htaccess? error on your web browser. Problem :

I have an .htaccess file with over 200 redirection rules. It seems some of them are conflicting each other.

Is there any way to find out which one is responsible of redirect on a particular request?

Please note, I'm using ISAPI_Rewrite from HeliconTech (similar syntax to Apache mod_rewrite) over IIS 6.

Solution :

Use RewriteLog and RewriteLogLevel directives to log such activity (IIS restart most likely will be required).

The higher value you put for RewriteLogLevel the more verbose/detailed it will be.

If your site is busy (has lots of requests) then you will have hard times debugging it (log will become huge in a matter of seconds/minutes and it will become quite hard to see what is going on there (where one request ends and another starts etc)) .. so try it on your dev machine or when not busy if possible.

We hope that this article has helped you resolve the htaccess, apache, redirects error in your web browsers. Enjoy browsing the internet uninterrupted!