blocks|key|1443744|text|您发布的代码看起来应该可以正确地删除表单身份验证令牌，因此可能存在问题的文件夹/页面实际上没有受到保护的情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1443745|您是否确认在登录之前无法访问这些页面？|1443746|您可以发布您正在使用的web.config设置和登录代码吗？|1443747|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

The code you posted looks like it should correctly remove the forms authentication token, so it is possible that the folders/pages in question are not actually protected.

Have you confirmed that the pages cannot be accessed before a login has occured?

Can you post the web.config settings and login code that you are using?

blocks|key|1658469|text|在我看来，您没有在中正确设置您的web.config授权部分。请参见下面的示例。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1658470|<authentication+mode="Forms">
++<forms+name="MyCookie"+loginUrl="Login.aspx"+protection="All"+timeout="90"+slidingExpiration="true"></forms>
</authentication>
<authorization>
++<deny+users="?"+/>
</authorization>|code-block|syntax|javascript|1658471|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Sounds to me like you don't have your web.config authorization section set up properly within . See below for an example.

<pre><code>&lt;authentication mode="Forms"&gt;
 &lt;forms name="MyCookie" loginUrl="Login.aspx" protection="All" timeout="90" slidingExpiration="true"&gt;&lt;/forms&gt;
&lt;/authentication&gt;
&lt;authorization&gt;
 &lt;deny users="?" /&gt;
&lt;/authorization&gt;
</code></pre>

blocks|key|1658569|text|您是否正在使用IE测试/查看此行为？IE可能正在从缓存中提供这些页面。众所周知，IE很难刷新它的缓存，所以在很多情况下，即使在你注销之后，输入其中一个“安全”页面的url也会显示以前缓存的内容。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1658570|(我曾经看到过这种行为，即使您以不同的用户身份登录，IE也会在您的页面顶部显示“欢迎”栏，其中包含旧用户的用户名。现在，通常重新加载会更新它，但如果它是持久的，它仍然可能是一个缓存问题。)|1658571|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Are you testing/seeing this behaviour using IE? It's possible that IE is serving up those pages from the cache. It is notoriously hard to get IE to flush it's cache, and so on many occasions, even after you log out, typing the url of one of the "secured" pages would show the cached content from before.

(I've seen this behaviour even when you log as a different user, and IE shows the "Welcome " bar at the top of your page, with the old user's username. Nowadays, usually a reload will update it, but if it's persistant, it could still be a caching issue.)

blocks|key|1658628|text|可能是您从一个子域(sub1.domain.com)登录，然后尝试从另一个子域(www.domain.com)注销。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1658629|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

It could be that you are logging in from one subdomain (sub1.domain.com) and then trying to logout from a different subdomain (www.domain.com).

blocks|key|1658719|text|我一直在为我的所有页面编写一个基类，我遇到了同样的问题。我有像下面这样的代码，但它不能工作。通过跟踪，控制从RedirectToLoginPage()语句传递到下一行，而无需重定向。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1658720|if+(_requiresAuthentication)
{
++++if+(!User.Identity.IsAuthenticated)
++++++++FormsAuthentication.RedirectToLoginPage();

++++//+check+authorization+for+restricted+pages+only
++++if+(_isRestrictedPage)+AuthorizePageAndButtons();
}|code-block|syntax|javascript|1658721|我发现有两种解决方案。将FormsAuthentication.RedirectToLoginPage()；修改为|1658722|if+(!User.Identity.IsAuthenticated)
++++Response.Redirect(FormsAuthentication.LoginUrl);|1658723|或者通过添加以下内容来修改web.config|1658724|<authorization>
++<deny+users="?"+/>
</authorization>|1658725|在第二种情况下，在跟踪时，控件没有到达请求的页面。在命中断点之前，它已被立即重定向到登录url。因此，问题不在于SignOut()方法，而在于重定向方法。|1658726|我希望这能帮助到一些人|1658727|问候|1658728|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Y|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|12|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|14|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|V|$]]

I have been writing a base class for all of my Pages and I came to the same issue.
I had code like the following and It didn't work. By tracing, control passes from RedirectToLoginPage() statement to the next line without to be redirected.

<pre><code>if (_requiresAuthentication)
{
 if (!User.Identity.IsAuthenticated)
 FormsAuthentication.RedirectToLoginPage();

 // check authorization for restricted pages only
 if (_isRestrictedPage) AuthorizePageAndButtons();
}
</code></pre>

I found out that there are two solutions.
Either to modify FormsAuthentication.RedirectToLoginPage(); to be 

<pre><code>if (!User.Identity.IsAuthenticated)
 Response.Redirect(FormsAuthentication.LoginUrl);
</code></pre>

OR to modify the web.config by adding

<pre><code>&lt;authorization&gt;
 &lt;deny users="?" /&gt;
&lt;/authorization&gt;
</code></pre>

In the second case, while tracing, control didn't reach the requested page. It has been redirected immediately to the login url before hitting the break point.
Hence, The SignOut() method isn't the issue, the redirect method is the one.

I hope that may help someone

Regards

blocks|key|1658781|text|用户仍然可以浏览您的网站，因为当您调用FormsAuthentication.SignOut()时不会清除cookies，而且每次新请求时都会对cookies进行身份验证。在MS文档中，是说cookie将被清除，但他们没有，bug？这和Session.Abandon()完全一样，cookie仍然存在。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1658782|您应该将您的代码更改为：|1658783|FormsAuthentication.SignOut();
Session.Abandon();

//+clear+authentication+cookie
HttpCookie+cookie1+=+new+HttpCookie(FormsAuthentication.FormsCookieName,+"");
cookie1.Expires+=+DateTime.Now.AddYears(-1);
Response.Cookies.Add(cookie1);

//+clear+session+cookie+(not+necessary+for+your+current+problem+but+i+would+recommend+you+do+it+anyway)
SessionStateSection+sessionStateSection+=+(SessionStateSection)WebConfigurationManager.GetSection("system.web/sessionState");
HttpCookie+cookie2+=+new+HttpCookie(sessionStateSection.CookieName,+"");
cookie2.Expires+=+DateTime.Now.AddYears(-1);
Response.Cookies.Add(cookie2);

FormsAuthentication.RedirectToLoginPage();|code-block|syntax|javascript|1658784|HttpCookie位于System.Web命名空间中。MSDN+Reference。|1658785|entityMap|0|LINK|mutability|MUTABLE|url|https://msdn.microsoft.com/en-us/library/system.web.httpcookie(v=vs.110).aspx)^0|J|T|3A|H|0|0|0|0|A|C|A|S|E|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]|$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|11|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|12|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|13|8|@$9|14|A|15|B|C]|$9|16|A|17|B|C]]|D|@$9|18|A|19|1|1A]]|E|$]]|$1|O|3|-4|5|6|7|1B|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]]]

Users can still browse your website because cookies are not cleared when you call <code>FormsAuthentication.SignOut()</code> and they are authenticated on every new request. In MS documentation is says that cookie will be cleared but they don't, bug?
Its exactly the same with <code>Session.Abandon()</code>, cookie is still there.

You should change your code to this:

<pre><code>FormsAuthentication.SignOut();
Session.Abandon();

// clear authentication cookie
HttpCookie cookie1 = new HttpCookie(FormsAuthentication.FormsCookieName, "");
cookie1.Expires = DateTime.Now.AddYears(-1);
Response.Cookies.Add(cookie1);

// clear session cookie (not necessary for your current problem but i would recommend you do it anyway)
SessionStateSection sessionStateSection = (SessionStateSection)WebConfigurationManager.GetSection("system.web/sessionState");
HttpCookie cookie2 = new HttpCookie(sessionStateSection.CookieName, "");
cookie2.Expires = DateTime.Now.AddYears(-1);
Response.Cookies.Add(cookie2);

FormsAuthentication.RedirectToLoginPage();
</code></pre>

<code>HttpCookie</code> is in the <code>System.Web</code> namespace. <a href="https://msdn.microsoft.com/en-us/library/system.web.httpcookie(v=vs.110).aspx" rel="noreferrer">MSDN Reference</a>.

blocks|key|1444101|text|我只是遇到了同样的问题，SignOut()似乎无法正确地删除票据。但仅在某些其他逻辑导致重定向的特定情况下。在我删除了第二个重定向(用一条错误消息代替它)之后，问题就消失了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1444102|问题一定是页面在错误的时间重定向，因此没有触发身份验证。|1444103|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I just had the same problem, where SignOut() seemingly failed to properly remove the ticket. But only in a specific case, where some other logic caused a redirect. After I removed this second redirect (replaced it with an error message), the problem went away.

The problem must have been that the page redirected at the wrong time, hence not triggering authentication.

blocks|key|1659724|text|这里的关键是你说“如果我直接输入一个URL+...”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1659725|默认情况下，在forms身份验证下，浏览器会为用户缓存页面。因此，直接从浏览器的地址框下拉菜单中选择一个URL，或者键入它，就可以从浏览器的缓存中获取页面，而再也不会返回到服务器来检查身份验证/授权。解决此问题的方法是在每个页面的Page_Load事件中或在基页的OnLoad()中防止客户端缓存：|1659726|Response.Cache.SetCacheability(HttpCacheability.NoCache);|code-block|syntax|javascript|1659727|您可能还想调用：|1659728|Response.Cache.SetNoStore();|1659729|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

The key here is that you say "If I type in a URL directly...".

By default under forms authentication the browser caches pages for the user. So, selecting a URL directly from the browsers address box dropdown, or typing it in, MAY get the page from the browser's cache, and never go back to the server to check authentication/authorization. The solution to this is to prevent client-side caching in the Page_Load event of each page, or in the OnLoad() of your base page:

<pre><code>Response.Cache.SetCacheability(HttpCacheability.NoCache);
</code></pre>

You might also like to call:

<pre><code>Response.Cache.SetNoStore();
</code></pre>

blocks|key|1659735|text|这对我很管用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1659736|public+virtual+ActionResult+LogOff()
++++{
++++++++FormsAuthentication.SignOut();
++++++++foreach+(var+cookie+in+Request.Cookies.AllKeys)
++++++++{
++++++++++++Request.Cookies.Remove(cookie);
++++++++}
++++++++foreach+(var+cookie+in+Response.Cookies.AllKeys)
++++++++{
++++++++++++Response.Cookies.Remove(cookie);
++++++++}
++++++++return+RedirectToAction(MVC.Home.Index());
++++}|code-block|syntax|javascript|1659737|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This works for me

<pre><code>public virtual ActionResult LogOff()
 {
 FormsAuthentication.SignOut();
 foreach (var cookie in Request.Cookies.AllKeys)
 {
 Request.Cookies.Remove(cookie);
 }
 foreach (var cookie in Response.Cookies.AllKeys)
 {
 Response.Cookies.Remove(cookie);
 }
 return RedirectToAction(MVC.Home.Index());
 }
</code></pre>

blocks|key|1659791|text|执行Session.abandon()并销毁cookie效果很好。我使用的是mvc3，如果你转到一个受保护的页面，注销并浏览你的浏览器历史记录，就会出现这个问题。没什么大不了的，但还是有点烦人。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1659792|尝试浏览我的web应用程序上的链接是正确的。|1659793|将其设置为不进行浏览器缓存可能是可行的。|1659794|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Doing Session.abandon() and destroying the cookie works pretty good. I'm using mvc3 and it looks like the problem occurs if you go to a protected page, log out, and go via your browser history. Not a big deal but still kinda of annoying.

Trying to go through links on my web app works the right way though.

Setting it to not do browser caching may be the way to go.

blocks|key|1445111|text|我现在有一个类似的问题，我相信在我的情况下的问题以及最初的海报是因为重定向。默认情况下，Response.Redirect会导致一个异常，该异常会立即冒泡，直到它被捕获并立即执行重定向，我猜这会阻止修改后的cookie集合向下传递到客户端。如果您修改代码以使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1445112|Response.Redirect("url",+false);|code-block|syntax|javascript|1445113|这可以防止异常，并且似乎允许将cookie正确地发送回客户端。|1445114|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I am having a similar issue now and I believe the problem in my case as well as the original poster is because of the redirect. By default a Response.Redirect causes an exception which immediately bubbles up until it is caught and the redirect is immediately executed, I am guessing that this is preventing the modified cookie collection from being passed down to the client. If you modify your code to use:

<pre><code>Response.Redirect("url", false);
</code></pre>

This prevents the exception and seems to allow the cookie to be properly sent back to the client.

blocks|key|1445183|text|我只是在这里尝试了一些建议，当我能够使用浏览器的后退按钮时，当我单击菜单选择时，该ActionResult的授权令牌会将我直接送回登录屏幕。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1445184|以下是我的注销代码：|1445185|++++++++FormsAuthentication.SignOut();
++++++++Response.Cookies.Remove(FormsAuthentication.FormsCookieName);
++++++++Response.Cache.SetExpires(DateTime.Now.AddSeconds(-1));
++++++++HttpCookie+cookie+=+HttpContext.Request.Cookies[FormsAuthentication.FormsCookieName];
++++++++if+(cookie+!=+null)
++++++++{
++++++++++++cookie.Expires+=+DateTime.Now.AddDays(-1);
++++++++++++Response.Cookies.Add(cookie);
++++++++}|code-block|syntax|javascript|1445186|尽管浏览器上的后退功能让我返回并显示了安全菜单(我仍在做这件事)，但我无法做任何在应用程序中受到保护的事情。|1445187|希望这能有所帮助|1445188|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I just tried some of the suggestions here and while I was able to use the browser back button, when I clicked on a menu selection the [Authorize] token for that [ActionResult] sent me right back to the login screen.

Here is my logout code:

<pre><code> FormsAuthentication.SignOut();
 Response.Cookies.Remove(FormsAuthentication.FormsCookieName);
 Response.Cache.SetExpires(DateTime.Now.AddSeconds(-1));
 HttpCookie cookie = HttpContext.Request.Cookies[FormsAuthentication.FormsCookieName];
 if (cookie != null)
 {
 cookie.Expires = DateTime.Now.AddDays(-1);
 Response.Cookies.Add(cookie);
 }
</code></pre>

Although the back function on the browser took me back and displayed the secured menu (I am still working on that) I was not able to do anything that was secured in the app.

Hope this helps

blocks|key|1659979|text|我已经在这个帖子中尝试了大多数答案，但没有成功。结果是这样的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1659980|protected+void+btnLogout_Click(object+sender,+EventArgs+e)
{
++++FormsAuthentication.Initialize();
++++var+fat+=+new+FormsAuthenticationTicket(1,+"",+DateTime.Now,+DateTime.Now.AddMinutes(-30),+false,+string.Empty,+FormsAuthentication.FormsCookiePath);
++++Response.Cookies.Add(new+HttpCookie(FormsAuthentication.FormsCookieName,+FormsAuthentication.Encrypt(fat)));
++++FormsAuthentication.RedirectToLoginPage();
}|code-block|syntax|javascript|1659981|在这里找到它：http://forums.asp.net/t/1306526.aspx/1|offset|length|1659982|entityMap|0|LINK|mutability|MUTABLE|url|http://forums.asp.net/t/1306526.aspx/1^0|0|0|7|12|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

I've tried most answers in this thread, no luck. Ended up with this:

<pre><code>protected void btnLogout_Click(object sender, EventArgs e)
{
 FormsAuthentication.Initialize();
 var fat = new FormsAuthenticationTicket(1, "", DateTime.Now, DateTime.Now.AddMinutes(-30), false, string.Empty, FormsAuthentication.FormsCookiePath);
 Response.Cookies.Add(new HttpCookie(FormsAuthentication.FormsCookieName, FormsAuthentication.Encrypt(fat)));
 FormsAuthentication.RedirectToLoginPage();
}
</code></pre>

Found it here: <a href="http://forums.asp.net/t/1306526.aspx/1" rel="nofollow">http://forums.asp.net/t/1306526.aspx/1</a>

blocks|key|1660025|text|只需在按log时尝试发送会话变量即可。在欢迎页面上，首先在页面加载或Init事件中检查该会话是否为空：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1660026|if(Session["UserID"]+==+null+%7C%7C+Session["UserID"]+==+"")
{
++++Response.Redirect("Login.aspx");
}|code-block|syntax|javascript|1660027|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Just try to send a session variable when you press log in.
And on the welcome page, first check whether that session is empty like this in the page load or in the Init Event:

<pre><code>if(Session["UserID"] == null || Session["UserID"] == "")
{
 Response.Redirect("Login.aspx");
}
</code></pre>

blocks|key|1445270|text|对于MVC，这对我来说是可行的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1445271|++++++++public+ActionResult+LogOff()
++++++++{
++++++++++++FormsAuthentication.SignOut();
++++++++++++return+Redirect(FormsAuthentication.GetRedirectUrl(User.Identity.Name,+true));
++++++++}|code-block|syntax|javascript|1445272|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

For MVC this works for me:

<pre><code> public ActionResult LogOff()
 {
 FormsAuthentication.SignOut();
 return Redirect(FormsAuthentication.GetRedirectUrl(User.Identity.Name, true));
 }
</code></pre>

blocks|key|1445308|text|经过多次搜索，这对我来说终于起作用了。我希望它能帮上忙。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1445309|public+ActionResult+LogOff()
{
++++AuthenticationManager.SignOut();
++++HttpContext.User+=+new+GenericPrincipal(new+GenericIdentity(string.Empty),+null);
++++return+RedirectToAction("Index",+"Home");
}

<li+class="page-scroll">@Html.ActionLink("Log+off",+"LogOff",+"Account")</li>|code-block|syntax|javascript|1445310|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

After lots of search finally this worked for me . I hope it helps.

<pre><code>public ActionResult LogOff()
{
 AuthenticationManager.SignOut();
 HttpContext.User = new GenericPrincipal(new GenericIdentity(string.Empty), null);
 return RedirectToAction("Index", "Home");
}

&lt;li class="page-scroll"&gt;@Html.ActionLink("Log off", "LogOff", "Account")&lt;/li&gt;
</code></pre>

blocks|key|1660110|text|对我来说，下面的方法是可行的。我认为如果"FormsAuthentication.SignOut()“语句后面有任何错误，SingOut就不能工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1660111|public+ActionResult+SignOut()
++++{
++++++++if+(Request.IsAuthenticated)
++++++++{
++++++++++++FormsAuthentication.SignOut();

++++++++++++return+Redirect("~/");
++++++++}
++++++++return+View();
+++++}|code-block|syntax|javascript|1660112|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

For me, the following approach works. I think if there is any error after the "FormsAuthentication.SignOut()" statement, SingOut doesn't work.

<pre><code>public ActionResult SignOut()
 {
 if (Request.IsAuthenticated)
 {
 FormsAuthentication.SignOut();

 return Redirect("~/");
 }
 return View();
 }
</code></pre>

Smashed my head against this a bit too long. How do I prevent a user from browsing a site's pages after they have been logged out using FormsAuthentication.SignOut? I would expect this to do it:

<pre><code>FormsAuthentication.SignOut();
Session.Abandon();
FormsAuthentication.RedirectToLoginPage();
</code></pre>

But it doesn't. If I type in a URL directly, I can still browse to the page. I haven't used roll-your-own security in a while so I forget why this doesn't work.

FormsAuthentication.SignOut() does not log the user out

身份验证

服务器

把我的头撞得太长了点。如何防止用户在使用FormsAuthentication.SignOut注销后浏览站点的页面？我希望这样做：FormsAuthentication.SignOut();Session.Abandon();FormsAuthentication.RedirectToLoginPage();如果我直接...

问FormsAuthentication.SignOut()不会注销用户
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问FormsAuthentication.SignOut()不会注销用户EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问FormsAuthentication.SignOut()不会注销用户
EN