ITmeze

Client has a bunch of domains and and websites. Because They have decided to change company’s name recently I was asked to proceed with chanage of domain names as well. After few weeks of constantly informing visitors about planned changed We decided that it is a good time to abandon old domains and redirect visitors to new ones. In order to “be okay” with google (their page ranks, indexed pages and so on) we make those redirects permanent (301 Moved Permanently as a response status code).

As all of the websites are hosted on IIS 7 I have decided to use URL Rewrite Module for the job. First of all – make sure You have Url rewrite module installed on Your server machine. Secondly, You need to update web.config file to something like the one that (assuming old-name):

  <system.webServer>
        ......
        <rewrite>
            <rules>
                <clear />
                <rule name="rebranding" enabled="false" stopProcessing="true">
                    <match url="(.*)" />
                    <conditions logicalGrouping="MatchAll" trackAllCaptures="true">
                        <add input="{HTTP_HOST}" pattern="(.*)old-name(.*)" />
                    </conditions>
                    <action type="Redirect" url="http://{C:1}new-name{C:2}/{ToLower:{R:1}}" appendQueryString="true" />
                </rule>                
            </rules>
        </rewrite>
  </system.webServer>

You can do that in IIS manager as well.
Some explanation here:

• match url=”(.*)” – matches all request
• trackAllCaptures=”true” – will enable to use captured grups in our redirect url
• (.*)old-name(.*) – matches each HTTP_HOST that has ‘old-name’ within, like: ar.old-name.com or www.old-name.ru
• http://{C:1}new-name{C:2}/{ToLower:{R:1}} – redirected url, R:1 stands for matches from and C:1 and C:2 matches those from conditions, ToLower changes text to lower case letters
• appendQueryString=”true” – will append query string to newly generated url

Have fun

Elmah - awesome library for asp.net that enable to log exceptions (as well as those that end up with Yellow screen of death). It comes with a great module and a handler used to view error logs. It really helps a lot. I used that in literally every web project I have made.

Yesterday, I was installing new project on fresh Windows Server 2008 R2.

I ended up with an error: Handler “Elmah” has a bad module “ManagedPipelineHandler” in its module list.

After hour of goggling I couldn’t find a solution that would solve my problem (reinstalling asp.net, changing ISAPI restrictions). Nothing helped. Then I have found out that problem lies in IIS7 configuration part in my web.config.

<system.webServer>
  <modules>
    <add name="ErrorLog" type="Elmah.ErrorLogModule, Elmah"/>
  </modules>
  <handlers>
    <add name="Elmah" path="elmah.axd" verb="POST,GET,HEAD" type="Elmah.ErrorLogPageFactory, Elmah" preCondition="integratedMode"   />
  </handlers>
</system.webServer>

My set up was done based on dotnetslackers article, and I simply copied their pre IIS7 configuration to system.webserver part. The part that I was missing was preCondition=”integratedMode” attribute for a handler.

Hope that helps someone