ISAPI Rewrite Issue

[bakedjake]

I have a simple rewrite rule:

RewriteRule /jake.sucks - [F]

Unfortunately, when I access that URL, I get a 404, not a 403. This message appears as the content of the page:

The requested resource could not be found.

ISAPI rewrite is working fine in other respects. All other redirects work - it's just that anytime I try to forbid stuff, I get that standard ISAPI Rewrite error message.

I know that message is ISAPI rewrites', because all other 404s are handled by our .NET error handler in global.asax.

[pageoneresults]

bakedjake, anything in your http.parse.errors file?

[bakedjake]

Not a thing...

This one is annoying. I've set up lots of ISAPI rewrite installations before, never with this problem.

This problem is manifesting itself across a number of servers, all configured the same way. So I'm wondering if there is a pecularity to the way these servers are set up and an interaction with ISAPI rewrite.

Win2k3 Enterprise/IIS 6.0 btw.

[pageoneresults]

Did you try sending an email to Yaroslav or posting in their forums about it? Unfortunately I think there are only about two of us here that work with ISAPI and one of us is Clueless (me). :)

[bakedjake]

Will try that next p1r, thanks.

[bakedjake]

Just for reference:

Alex from Helicon Tech Support got back to me - thanks Alex!

He says that this error is by design, and ISAPI Rewrite follows IIS 6 standard behavior to return 404 for disallowed resources.

He also mentions that if we need to return a 403, we'll have to produce our own asp page that returns a 403 and rewrite to it.