How to redirect an entire address in IIS7 URL Rewrite

iis-7redirectrewrite

My company has a promotion in a magazine that was created before we implemented our new site. Since the release of the new site we use a inbound rewrite rule to redirect anything with a www. This advertisement however is http://www.openeye.net/2011rspromo/ so when a user visits it it redirects back to the homepage.

I need it to redirect to http://openeye.net/promotions/reportstar-free-cm-610/ instead and can't seem to find the right combination in URL Rewrites to get it to work.

Any help would be appreciated.

Default www redirect
enter image description here

What I'm trying to do
enter image description here

Best Answer

It is a better approach to this issue to register an additional www.openeye.net as an additional host header for the openeye.net site.

You can do this in IIS7 by right-clicking the site and selecting Edit Bindings. There should be one default binding such as

 Type        Host Name        Port        IP Address
 http        openeye.net       80         00.00.00.000*

**This should be either the IP of your server or "All Unassigned".*

Click Add, then enter a new binding with all of the same information, except that the Host name should read "www.openeye.net" instead of "openeye.net". When you are done your binding will look like:

 Type        Host Name        Port        IP Address
 http        openeye.net       80         00.00.00.000
 http        www.openeye.net   80         00.00.00.000

Please note that this will not actually redirect the request for http://www.openeye.net/2011rspromo/ to http://openeye.net/2011rspromo/, but will bind any such requests to the intended location. So, both URLs will resolve to the same resource.

Correct way in new versions of nginx

Turn out my first answer to this question was correct at certain time, but it turned into another pitfall - to stay up to date please check Taxing rewrite pitfalls

I have been corrected by many SE users, so the credit goes to them, but more importantly, here is the correct code:

server {
       listen         80;
       server_name    my.domain.com;
       return         301 https://$server_name$request_uri;
}

server {
       listen         443 ssl;
       server_name    my.domain.com;
       # add Strict-Transport-Security to prevent man in the middle attacks
       add_header Strict-Transport-Security "max-age=31536000" always; 

       [....]
}

IIS 7 URL rewrite rule

A rewrite needs to be a relative path on disk, under the same website. That's what is causing the 404 error in your case.

A redirect will send a client-side redirect, but that won't work since 192.168.1.11 is an internal IP that can't be accessed publicly.

What you need is ARR: http://www.iis.net/expand/ApplicationRequestRouting. It's a reverse proxy and will take the public request and forward it on to the internal server. This is the middle man between the client and the internal server. It leverages IIS and URL Rewrite so you're already much of the way there.

Best Answer

Related Solutions

NGINX Redirect – How to Rewrite All HTTP Requests to HTTPS While Maintaining Sub-Domain

Correct way in new versions of nginx

IIS 7 URL rewrite rule

Related Topic