角度评论指令 - 目的/意图/最佳实践(Angular Comment Directive - Purpose / Intent / Best Practice)

 通常这应该自动发生。 当匿名用户访问受保护的资源时（他是匿名的，因为他的会话过期），FormsAuthentication模块截获这些请求并通过追加指向受保护资源的ReturnUrl查询字符串参数重定向到您在web.config中注册的loginUrl 。 
 
 因此，例如，如果您将~/Account/LogOn配置为您的登录网址，并且匿名用户尝试点击~/Foo/Bar受保护的资源，他将被重定向到~/Account/LogOn?ReturnUrl=%2FFoo%2FBar 。 
 
 然后，他将看到一个登录页面，在那里他将输入他的凭据并将该表单提交给Account控制器上的[HttpPost] LogOn操作。 凭证将被验证，如果有效，将生成一个新的表单身份验证cookie，并将用户重定向到最初请求的受保护资源。 
 
 以下是LogOn操作的相应代码： 
 
[HttpPost]
public ActionResult LogOn(LogOnModel model, string returnUrl)
{
    if (ModelState.IsValid)
    {
        if (Membership.ValidateUser(model.UserName, model.Password))
        {
            FormsAuthentication.SetAuthCookie(model.UserName, model.RememberMe);
            if (Url.IsLocalUrl(returnUrl) && returnUrl.Length > 1 && returnUrl.StartsWith("/")
                && !returnUrl.StartsWith("//") && !returnUrl.StartsWith("/\\"))
            {
                return Redirect(returnUrl);
            }
            else
            {
                return RedirectToAction("Index", "Home");
            }
        }
        else
        {
            ModelState.AddModelError("", "The user name or password provided is incorrect.");
        }
    }

    // If we got this far, something failed, redisplay form
    return View(model);
}
 
 请注意，成功验证后，用户是如何重定向到默认Home/Index或returnUrl参数的。 
 
 当然，我在这里讲的所有这些故事都适用于由Visual Studio创建的默认ASP.NET MVC模板。 如果由于某种原因您修改了此模板，这可能会解释您正在观察的行为。 
 
 在任何情况下，从我的回答中要记住的事情是，如果您使用的是表单身份验证，则该模块将作为ReturnUrl查询字符串参数将最初请求的受保护资源传递到配置的登录页面。 因此，在成功验证后，您需要将用户重定向到此页面。 

Normally this should happen automatically. When an anonymous user hits a protected resource (he is anonymous because his session expired), the FormsAuthentication module intercepts this requests and redirects to the loginUrl you registered in your web.config by appending a ReturnUrl query string parameter pointing to the protected resource.
 
So if for example you configured ~/Account/LogOn to be your logon url, and the anonymous user attempts to hit the ~/Foo/Bar protected resource he will be redirected to ~/Account/LogOn?ReturnUrl=%2FFoo%2FBar.
 
Then he will be presented with a login page where he will input his credentials and submit the form to the [HttpPost] LogOn action on the Account controller. The credentials will be validated and if valid, a new forms authentication cookie will be generated and the user redirected to the initially requested protected resource.
 
Here's the respective code from the LogOn action:
 
[HttpPost]
public ActionResult LogOn(LogOnModel model, string returnUrl)
{
    if (ModelState.IsValid)
    {
        if (Membership.ValidateUser(model.UserName, model.Password))
        {
            FormsAuthentication.SetAuthCookie(model.UserName, model.RememberMe);
            if (Url.IsLocalUrl(returnUrl) && returnUrl.Length > 1 && returnUrl.StartsWith("/")
                && !returnUrl.StartsWith("//") && !returnUrl.StartsWith("/\\"))
            {
                return Redirect(returnUrl);
            }
            else
            {
                return RedirectToAction("Index", "Home");
            }
        }
        else
        {
            ModelState.AddModelError("", "The user name or password provided is incorrect.");
        }
    }

    // If we got this far, something failed, redisplay form
    return View(model);
}
 
Notice how the user is redirected either to the default Home/Index or to the returnUrl parameter upon successful authentication.
 
Now of course all this story that I told here is true for the default ASP.NET MVC template created by Visual Studio. If for some reason you have modified this template this might explain the behavior you are observing. 
 
In any case the thing to remember from my answer is that if you are using Forms Authentication, the module will pass as ReturnUrl query string parameter the initially requested protected resource to the configured logon page. So it's up to you to redirect the user to this page upon successful authentication.