The first log snip you showed was a request for a .gif file. It's not "going through your directories" - and I don't know what you mean by that. The web page has a .gif in it, and IIRF is checking to see if any of the rules match
that .gif. No rules match, so you get no rewrite (and no redirect).
In every attempt I make, I give an exact file extension (.aspx). So it didn't make since to me that it should be looking at .gifs or anything else in a page. Also, if its a redirect, Shouldn't it be responding to the server request. Why would it look through
everything on the page? My interpretation of the log file was that it was trying to match to a file on the system. Your documentation does not explain this.
Also - the replacement pattern should not get a terminating $.
I use the terminating $ because you do in your examples:
RedirectRule ^/(W.*)$ http://server.dyndns.org:7070/$1 [R=301]
I read the part in the section on regualar expressions that says the $1 is to identify a group. But that page doesn't make it clear if the terminating $ is needed in all cases or just when you want to identify that group.
why did you remove the http:// prefix on from the redirect target?
I will add this and see if anything works differently.
For the record, I read your manual. Its not particularly clear on any of the issues you point out here. Think about how much traffic this discussion group gets: If your documentation was that great, do you really think you'd have regular posts to respond
to? People come here with different levels of knowledge, but even experienced guys end up coming here because a lot of documentation is poorly organized and vague. You give poor examples and there is nothing intuitive about your approach to the topics.
I appreciate that you do this for free. I thank you for your help. But maybe you should work on your communication skills. I didn't ask for your software, I got stuck with it. I'm looking for answers, not condescension. I've done this same task on
4 other sites with ISAPI_Rewrite. And about 5 sites with Apache mod_rewrite.
The final statement in your response is rude & unnecessary:
I know you said you are new to this stuff, but I would recommend not
using IIRF in production if you have not read the documentation.