I'm getting this unexpected behavior from asp.net core which I'm starting to learn.
I have a below form in my View:
<form asp-controller="Account" asp-action="Login" method="post">
<button type="submit">LOGIN</button>
</form>
Yes I'm using tag helpers here. And here is the controller:
public class AccountController : Controller
{
[HttpPost]
[AllowAnonymous]
public async Task<IActionResult> Login(string returnUrl)
{
if (string.IsNullOrEmpty(returnUrl) || !Url.IsLocalUrl(returnUrl))
return RedirectToAction("index", "home");
else
return LocalRedirect(returnUrl);
}
}
Now as per my understanding thus far, returnUrl should automatically get query string value if it is there in query string. But with this setup it is not happening. After a lot of head scratching I found a solution online to change in my view into this:
<form method="post">
<button type="submit">LOGIN</button>
</form>
and then it starts working. But why is this behavior there, what is causing this, why form tag helpers not letting query string to bind for this post method form ???
If you use default form without tag helper,it would get the query string by default.
If you use tag helper to specify the controller and action,your code would translate into:
<form method="post" action="/Account/Login">
This caused that returnUrl always be null.
For getting the returnUrl,you need to specify the route by using asp-route-{value} like below,otherwise,it would get into the default route templete:
<form asp-controller="Account" asp-action="Login" asp-route-returnUrl="yourUrl" method="post">
<button type="submit">LOGIN</button>
</form>
This would translate into:
<form method="post" action="/Account/Login?returnUrl=yourUrl">
Reference: