Asp.Net MVC 301 Redirects

Question

We used to use ISAPI Re-Write (Infact its still on our server) although it doesnt work with ASP.Net MVC (Somthing to do with 'euxd' get param).

We need a relaiable way to implement simple 301 redirects, when we change the site structure, upload a new site etc. Any suggestions?

Ok, it I wanted to redirect /SomeFolder/SomePage.HTML?Param1=X to /NewPage/X

How can we do that?

Are you wanting to redirect *non-MVC* page requests to an MVC controller action as in your example? — Nathan Taylor, Feb 11 '11 at 22:19
Correct, so OLD pages (Previous site written in PHP) to the new pages written in .Net MVC 3 — LiamB, Feb 11 '11 at 22:21
What version of IIS are you going to be running on the new server? — Charlino, Feb 12 '11 at 00:06
If you are using IIS7, I would recommend using the official IIS7 URL Rewrite Module. See answer below. — Charlino, Feb 14 '11 at 17:50

score 37 · Answer 1 · edited Sep 30 '14 at 16:35

37

In MVC 3 there are three new redirect methods that can be used in controllers to redirect permanently (produce a 301); as opposed to the 302s (temporary redirect) produced by the MVC 2 redirects.

RedirectPermanent
RedirectToActionPermanent
RedirectToRoutePermanent

public ActionResult OldAction()
{
  return RedirectPermanent(urlname);
}

There is a great tutorial in the Controllers section of these walkthroughs on PluralSight.

edited Sep 30 '14 at 16:35

bressain

899
9
20

answered Feb 11 '11 at 09:59

amelvin

8,919
4
38
59

1

You'll need a `return` in there too. – Ian Mercer Feb 27 '11 at 02:45
1

Hightechrider - added the return statement – Mr. Flibble Apr 12 '11 at 08:34

score 3 · Accepted Answer · answered Feb 14 '11 at 17:48

3

If you are using IIS7, I would recommend using the official IIS7 URL Rewrite module.

answered Feb 14 '11 at 17:48

Charlino

15,802
3
58
74

Just found this, perfect for what we need!! – LiamB Feb 14 '11 at 22:03

score 2 · Answer 3 · answered Feb 11 '11 at 22:49

To perform a redirect from a non-MVC page to an MVC controller action your best bet is to use a library like UrlRewriting.net or similar which uses an HttpModule to process each request and dispatch it to a specific location.

Example: Redirect requests for '/faq.asp' to '/faq':

<add name="faq.asp" virtualUrl="^~/faq.asp([\?#].*)?$"
            destinationUrl="~/faq"
            redirect="Application"
            redirectMode="Permanent"
            ignoreCase="true" />

When you add the HttpModule that powers UrlRewriting.Net to your Web.config, make sure you define it before the UrlRoutingModule which is defined by ASP.NET automatically. Otherwise, ASP.NET will attempt to handle your request by mapping it to a a file or controller and you may experience some unexpected problems as a result.

<modules runAllManagedModulesForAllRequests="true">
    <add name="UrlRewriteModule" type="UrlRewritingNet.Web.UrlRewriteModule, UrlRewritingNet.UrlRewriter"/>
    <add name="UrlRoutingModule" type="System.Web.Routing.UrlRoutingModule, System.Web.Routing, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
</modules>

score 1 · Answer 4 · answered Nov 27 '11 at 10:44

1

I just blogged about a simple solution that uses ASP.NET MVC and an XML file to store the 301 redirect mappings.

However, as per Nathan Taylor's answer, if you need to do Regex based mapping, I would suggest using UrlRewriting.Net.

answered Nov 27 '11 at 10:44

Ben Foster

34,340
40
176
285

score 0 · Answer 5 · answered Feb 11 '11 at 09:56

0

Implement custom ActionResult. Example: http://www.stum.de/2008/10/22/permanentredirectresult/

answered Feb 11 '11 at 09:56

Lukáš Novotný

9,012
3
38
46

Asp.Net MVC 301 Redirects

5 Answers5

Linked