I'm trying to find a solution to a problem and I think your IIRF may be the answer. Would you please help me by answering this question?
I am building a Sharepoint (MOSS 2007) internet website. The client wants the URL to be re-written, like this:
1. website is at www.mysite1.com
2. visitor enters www.mysite2.com
3. client wants the visitor to arrive at www.mysite1.com but have www.mysite2.com remain in the browsers address
I believe this is server-side forwarding, or re-writing (are they the same thing?)
I've found the text, below, in the IIRF documentation. Does this mean that IIRF cannot help me with this problem? If it can help me, do you have any rules I could try? If it cannot help me, do you have any suggestions? I can see you have a lot of experience
in this area.
Is your July 15 post, here
http://stackoverflow.com/questions/550505/url-rewriting-with-iis-6-7-rewriting-host-name-httphost the answer to my problem?
Either way, many thanks for your valuable contribution to the community!
Apache's mod_rewrite includes the ability to specify local or remote forwarding. This is specified with an optional, third argument to the RewriteRule directive in the .properties or .htaccess file. This feature of Apache mod_rewrite is not supported
by Ionic's ISAPI rewrite filter.
IIRF does not do forward or reverse request proxying, like Apache's mod_proxy.
Unlike the combination of Apache's mod_rewrite and mod_proxy, IIRF is a simple and basic rewriting filter. Once a request is received within an IIS, IIRF can change the request to "something else", but the request stays on the box, and within
the given IIS server on the box. Redirects can be forwarded off the box, but these forward actions are not transparent - they are client-side redirects. See the doc for the RedirectRule directive above for more details.