I need to take a particular action if a user logs in from the home page. In my LogOnModel, I have a hidden field:
@Html.Hidden("returnUrl", Request.Url.AbsoluteUri)
In my Controller, I need to check if that value is the Home page or not. In the example below, I'm checking to see if the user is on a particular page ("Account/ResetPassword"). Is there a way to check to see if they're on the home page without resorting to regular expressions?
[HttpPost]
public ActionResult LogOnInt(LogOnModel model)
{
if (model.returnUrl.Contains("/Account/ResetPassword"))
{
return Json(new { redirectToUrl = @Url.Action("Index","Home")});
}
Any ideas? A million thanks!
You can check the Request. HttpMethod property. Save this answer.
A controller is responsible for controlling the way that a user interacts with an MVC application. A controller contains the flow control logic for an ASP.NET MVC application. A controller determines what response to send back to a user when a user makes a browser request.
ASP.NET MVC is no longer in active development. The last version update was in November 2018. Despite this, a lot of projects are using ASP.NET MVC for web solution development. As to JetBrains' research, 42% of software developers were using the framework in 2020.
One way to approach this would be to look for the specific controller in the RouteData
. Assuming that the controller you are using for the home page is called "HomeController", then the RouteData
for the request would contain the value "Home" for the key "Controller".
It would look something like this:
instead of (or in addition to if you have other reasons for it):
@Html.Hidden("returnUrl", Request.Url.AbsoluteUri)
you would have:
@Html.Hidden("referrer", Request.RequestContext.RouteData.Values['Controller'])
and your controller would look like:
[HttpPost]
public ActionResult LogOnInt(LogOnModel model)
{
if (model.referrer = "Home")
{
return Json(new { redirectToUrl = @Url.Action("Index","Home")});
}
}
This would eliminate the need for using .Contains()
Update:
You could also eliminate the need for a hidden field (and thereby reduce overall page-weight for what would seem like every page in your application) by mapping the referrer url (Request.UrlReferrer.AbsoluteUri
) to a route. There is a post about that here.
How to get RouteData by URL?
The idea would be to use the mvc engine to map a referrer url to an MVC route in the LogOnInt
method, allowing the code to be entirely self contained.
This would probably be cleaner than putting the controller name and action name out there for the world to see along with scripting to push it back to the server.
You can get the current URL via
string controller = (string)ViewContext.RouteData.Values["controller"];
string action = (string)ViewContext.RouteData.Values["action"];
string url = Url.Action(action, controller);
You can do this in an HtmlHelper or in the controller that renders the login view.
Store url
in a hidden field as you did, then in your post action:
[HttpPost]
public ActionResult LogOnInt(LogOnModel model)
{
// Create your home URL
string homeUrl = Url.Action("Index", "Home");
if (model.referrer == homeUrl)
{
return Json(new { redirectToUrl = @Url.Action("Index","Home")});
}
}
The benefit of using Url.Action
is that it will use your route table to generate the URL, meaning if your routes ever change, you won't have to change this code.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With