IIS redirect based on domain/ ip address

iis-7

We have domain http://mysite.companyname.net which points to an ASP.net MVC site.

We also have a dedicated link from our office to the same server at the data centre in Manchester.

Is it possible to redirect any url belonging to mysite.companyname.net to http://mysite.companyname.net/maintenance.aspx.

However when we access it via it's internal machine name i.e. http://IIS-SERVER001 it works as normal

This is purely so we can test the site we deployed but customers can't use it while we're testing.

Also occasionally we need to redirect all uk customers to a certain url but allow German customers through e.g. example on uk bank holidays. how is this possible?

Best Answer

You would use the IIS Rewrite module for your first question.

It allows you to set up rules to change/block requests based on various things including the host name.

The documentation for the module is okay and there are lots of questions about it on here as well.

The bank holiday problem is a bit more tricky as the builtin URL rewrite rules can not handle such a requirement.

You may be able to write a Custom Rewrite Provider` for the URL rewrite module, otherwise you have to add such logic to your own http module which handle all requests coming in.

The problem is you don't want to do an IP location lookup on every request, so you would need to cache this.

It would be much easier if the Germans would always go to `

http://mysite.companyname.net/de/*

then you can have different rules for that part of the site.

Related Solutions

IIS 7 doesn’t do a 301 redirect

Can you give more details about the error you are getting? My first guess is that the StaticFile handler mapping is not present (or not configured properly). In the Handler Mappings setup, you should have a Module Mapping with the following settings:

name: StaticFile
path: *
type: StaticFileModule,DefaultDocumentModule,DirectoryListingModule

Request Restrictions:
mapping: invoke on file or folder
verbs: all
access: read

If this is the problem, you would be getting a 404.4/not found error, with sub error "the resource you are looking for does not have a handler associated with it"

IIS 7 – Setting Up Reverse Proxy Based on Domain Name

Since you're relying on the domain name rather than IP (which is easier in this situation), here's the most straight forward way of doing this:

make sure that your outside-facing server has bindings for the 3 sites based on the host header (website1.mydomain.com, etc). You can leave the IP address as (All unassigned). You probably have this done already. -- Basically what I mean is to add a binding to the first site that is "website1.mydomain.com", and to the other two sites in a similar way. Here's a walkthrough on bindings.
create 2 Web Farms in ARR on the ARR server. One to internalserver and the other to internalserver2. Use the primary IPs of those servers. You can setup 3 different Web Farms if you want unique health checks for each website. It's ok that two of them point to the same server. -- Steps: Create a new Server Farm called InternalServer and add a single server to it, which is "internalserver". Then create another Server Farm called InternalServer2, and add just "internalserver2" to it.
on the last step of the wizard when creating the site, when it asks if you want ARR to create a rule for you, only say 'yes' the first time. Take note of the rule that it creates so that you can learn from it. Then delete it. You want to manage your own rules. -- I'll explain the rules in the next step.
you should then set 3 URL Rewrite rules at the global level (IIS Server node, not the website node). URL = .*, use a condition with {HTTP_HOST} for your domain name, and the action should route to the corresponding webfarm. -- Here's an intro to URL rewrite. Follow those steps and enter a rule like the one below:

Example URL Rewrite:

<rule name="site1" patternSyntax="ECMAScript" stopProcessing="true">
  <match url=".*" />
  <conditions logicalGrouping="MatchAll">
    <add input="{HTTP_HOST}" pattern="^website1\.mydomain\.com$" />
  </conditions>
  <action type="Rewrite" url="http://InternalServer1/{R:0}" />
</rule>

Best Answer

Related Solutions

IIS 7 doesn’t do a 301 redirect

IIS 7 – Setting Up Reverse Proxy Based on Domain Name

Related Topic