Redirection still working after removing rule from ISAPI

[lalitmishra1988 Profile]

Hi,

I have written some rules to redirect some urls to other one and it were working fine....
But when i removed these rules from the httpd.conf file, redirection is still working. Please suggest me the solution.

[HeliconAndrew]

Hello,

It could be browser caching.
OR
You can try to recycle the pool of the site.

Regards
Andrew

[lalitmishra1988 Profile]

Hi Andrew,

I have done the same but still not working...

[HeliconAndrew]

Hello,

Try to find a duolicate of your rule among .htaccess or httpd.conf files. Sometimes our customers put rules all over the server and then don't know which one is working.

Ape doesn't cache rules

Regards
Andrew

[lalitmishra1988 Profile]

I have only 1 server with 1 httpd.conf file...Initially I entered only 1 rule in that file then redirection was working but when i removed that rule from file; redirection is still working. Currently my .conf file has below content only --

Code: Select all

# Helicon ISAPI_Rewrite configuration file
# Version 3.1.0.99

RewriteEngine on
RewriteBase /

#enabling rewrite.log
RewriteLogLevel 9
#enabling error.log
LogLevel debug

[HeliconAndrew]

If so, the only thing would be to do iisreset. It will force ISAPI_Rewrite to re-initialize.

Regards
Andrew

[lalitmishra1988 Profile]

I don't know what is happening on my server but even IISRESET could not work.

[HeliconAndrew]

Than it's not ISAPI_Rewrite that is doing it.
You may send us an email and we'll arrange remote access to your server to take a look.

[ChickPea Profile]

I don't know what is happening on my server but even IISRESET could not work.

Have you tried with a different browser? I've had problems before when a 301 rule is wrong- the browser remembers them long after the rule is removed. You can totally clear the browser cache, or clear it for the site in question in some browsers. The quick test for this is to, say, use Opera when you normally use Chrome to test. If the problem goes away, it's browser and not server.

This is kind-of the point of a 301 - permanent redirect.

[ArtsHub Profile]

Hey Guys,

I have been having the same issue in the past few days, we are rebuilding our sites and changing our url structures slightly.

If I write a rule and run then access that url, the rewrite rule (usually a 301) works fine, however if I remove the rule from my .htaccess and try again, the redirection persists from the old rule.

This is not isapi, it is definitely browsers trying to be too smart caching the redirection.
I proved this time and time again in the past 2 days by removing rules -> still got the old redirection consistently, UNTIL I kill my browser cache!
Then only do I get the correct result.

This is true in Firefox, Chrome and IE..
I've never experienced this before, and I've used Isapi rewrite for about 4 yrs or so.
Is this browsers trying to get too smart, or is this something that has always been the case?

I thought ISAPI Rewrite was supposed to intercept all urls between the users request and serving the request to the Server....

Please help Helicon gurus

Errol