Rewrite Caching

[TimButterfield Profile]

Hi,

We've recently upgraded to 3.1.0.73 of the Rewriter on Windows 2003 and have been getting some interesting behaviour.

Some of the redirects don't work. So to isolate the cause we added a new rewrite rule at the top > RewriteRule ^blah http://www.google.co.uk [NC, R=301]

This worked fine, so we moved it down the rewrites to see if there was a rule that would interfere. It continued to work and to prove it we'd change from google to use other redirect endpoints. Until we move it to a certain point in the list of rewrites. It then broke, so we moved up back up the writes to a position where we knew it had previously worked. The redirect then failed to work at all irrespective of where we placed the rewrite rule.

Is there any form of caching, or anything else that we need to be aware of that could be causing this as we've currently no confidence in our capacity to add new rewrites rules and have recently had to pull rewrites in to our code base.

Thanks
Tim

[HeliconAndrew]

Hello,

There's no caching.
Config files are read every time they are changed, unless permissions are set correctly permissions.
Please, provide the rewrite.log for the testing request.
Logging issues described in FAQ

Regards
Andrew