How to RedirectToAction in ASP.NET MVC without losing request data

How to RedirectToAction in ASP.NET MVC without losing request data

"Using ASP.NET MVC there are situations (such as form submission) that may require a RedirectToAction.

One such situation is when you encounter validation errors after a form submission and need to redirect back to the form, but would like the URL to reflect the URL of the form, not the action page it submits to.

As I require the form to contain the originally POSTed data, for user convenience, as well as validation purposes, how can I pass the data through the RedirectToAction()? If I use the viewData parameter, my POST parameters will be changed to GET parameters."

Asked by: Guest | Views: 447

Total answers/comments: 4

Comments display order:

Guest [Entry]

"The solution is to use the TempData property to store the desired Request components.

For instance:

public ActionResult Send()
{
TempData[""form""] = Request.Form;
return this.RedirectToAction(a => a.Form());
}

Then in your ""Form"" action you can go:

public ActionResult Form()
{
/* Declare viewData etc. */

if (TempData[""form""] != null)
{
/* Cast TempData[""form""] to
System.Collections.Specialized.NameValueCollection
and use it */
}

return View(""Form"", viewData);
}"

Guest [Entry]

Keep in mind that TempData stores the form collection in session. If you don't like that behavior, you can implement the new ITempDataProvider interface and use some other mechanism for storing temp data. I wouldn't do that unless you know for a fact (via measurement and profiling) that the use of Session state is hurting you.

Guest [Entry]

"Take a look at MVCContrib, you can do this:

using MvcContrib.Filters;

[ModelStateToTempData]
public class MyController : Controller {
//
...
}"

Guest [Entry]

"There is another way which avoids tempdata. The pattern I like involves creating 1 action for both the original render and re-render of the invalid form. It goes something like this:

var form = new FooForm();

if (request.UrlReferrer == request.Url)
{
// Fill form with previous request's data
}

if (Request.IsPost())
{
if (!form.IsValid)
{
ViewData[""ValidationErrors""] = ...
} else {
// update model
model.something = foo.something;
// handoff to post update action
return RedirectToAction(""ModelUpdated"", ... etc);
}
}

// By default render 1 view until form is a valid post
ViewData[""Form""] = form;
return View();

That's the pattern more or less. A little pseudoy. With this you can create 1 view to handle rendering the form, re-displaying the values (since the form will be filled with previous values), and showing error messages.

When the posting to this action, if its valid it transfers control over to another action.

I'm trying to make this pattern easy in the .net validation framework as we build out support for MVC."