Как Вы программно заканчиваете сессию в asp.net когда Сессия. Отказ () не работает?
Вы можете установить прокси-порты в catalina-server.xml в расположении хранилища / conf / tomcat [1]. Для порта 9443 вы можете установить порт 443 и перезапустить сервер.
[1] - https://docs.wso2.com/display/Carbon440/Adding+a+Custom+Proxy+Path
6 ответов
This is most likely because your SessionMode is not InProc (the only one that can detect when a session ends).
Quoted from MSDN:
Session Events
ASP.NET provides two events that help you manage user sessions. The Session_OnStart event is raised when a new session starts, and the Session_OnEnd event is raised when a session is abandoned or expires. Session events are specified in the Global.asax file for an ASP.NET application.
The Session_OnEnd event is not supported if the session Mode property is set to a value other than InProc, which is the default mode.
Session.Abandon() is the way to end a session. What is the problem you are encountering?
If its Back button related, that is a completely different issue ( page doesn't postback on Back, instead it runs one from clientside cache so no server side methods will execute).
Additionally, Session_End is problematic. It will only fire on Session.Abandon() when using InProc sessions, so if you are using a different Session mode, it cannot be relied on. Otherwise, Session_End will fire when SessionTimeout is reached ( default is 20 minutes I believe, configured in Web.Config ).
Have you tried using the following?
System.Web.Security.FormsAuthentication.SignOut();
This will clear cookies used for form authentication, although may not be what you're looking for.
You may need to use this in addtion to Session.Abandon()
Если сеансы сохраняются, вы можете попробовать (in web. config):
<sessionState regenerateExpiredSessionId="true">
Вот статья, в которой говорится о том, когда вызывается конец сеанса:
http://www.highoncoding.com/Articles/108_When_is_Session_End_Called__.aspx
It depends, if you have your application at 2 servers: 1 WebApplication that has its own session, and the second WS or WCF application that also has its own session, how it was in an application on which I was working once. Than if you have this case, the session must be ended at second point, and the first is ended the timeout appears. At least you'll have to use a token and to keep the list of tokens, of active sessions. May be it is your case. good luck. PS. To kill the session manage it in the second server.