如何重定向到ASP.NET MVC中的调用页面？

Question

Let's say I have a controller action that deletes an item out of a user's shopping basket. This controller action is triggered by performing a POST to the url ~/delete/{id}. If I have several pages on my application that will post to this url, how do I construct the controller action to redirect back to the page that posted to it?

Answer 1

That's what I do:

    public ActionResult ResendActivationEmail()
    {
        // Do other things here
        return new RedirectResult(Request.UrlReferrer.AbsoluteUri);
    }

Answer 2

You should provide a RedirectToUrl parameter from the posting page.

Relying on referrer headers is not a good practice.

Instead, do something like this:

public ActionResult Delete(int id, string RedirectToUrl)
{
  // check if RedirectToUrl is null or empty and redirect accordingly
}

On the posting view or partial view you can provide the parameter in several ways:

<%= Html.Hidden("RedirecToUrl","/my/lovely/url") %>

or

<form action="/item/delete/22?RedirectToUrl=/my/lovely/url">

I'd prefer the first option.

Answer 3

The first thing that I would do is use Ajax.ActionLink, then if the user has Javascript turned on, you'd never actually leave the page. This is the best solution. If you don't want a link, you could also have an Ajax form. Either of these could use the DELETE or POST method.

In order to handle the case where Javascript is turned off, when you detect in the controller that the POST was not done with Ajax (Request.IsAjaxRequest is false), you could look at the Request.UrlReferer property to get the Url of the referring page. If this is not null, you can use a RedirectResult to go back to this page. If it is null, choose a default landing page -- probably something like "Your item has been removed, click here to continue shopping." This latter will probably only rarely get hit.

Answer 4

我从来没有尝试过，但您可以使用Referer标头来了解post或get的来源，并尝试将URL与路由匹配。

Answer 5

Just use the URL Referer [sic] header.

var requestFrom = Request.UrlReferrer

You can find the documentation at: http://msdn.microsoft.com/en-us/library/system.web.httprequest.urlreferrer.aspx

The only time this wouldn't work is when the page is requested directly, but in that case you wouldn't have any place to redirect to anyways.

There is also the option of doing the only thing async using AJAX, so that your Delete action only does what it describes and isn't responsible for doing something outside of its intended purpose of deleting.

Answer 6

If you are using WCSF (Web Client Software Factory) to implement MVC pattern, you could use PageFlow to do all navigation.

Eg:-

PageFlow.Next(); or PageFlow.Previous();