I
Igor K
Hi,
I'm intercepting http requests coming to my asp.net application in order to
do some additional processing of html pages.
I'm having problems to access my variables stored in Session Object, that
always has IsSessionNew = TRUE. I can not figure out why is that. I expect
to have Session access in "Public Sub ProcessRequest(ByVal context As
HttpContext)" event. Is this correct? Or maybe to early/late? Of course I'm
using IRequireSessionState or IReadOnlySessionState, however none of this
work.
From the other side, SessionID inside of this session object seems to be ok,
it coresponds to ID stored in the cookie that I see
(context.Request.Cookies("ASP.NET_SessionId"). Is there a way to 'remind'
session object that it's instance is already alive on webserver?
So far I checked my web.config, IIS settings, I was experimenting with
global.asax events, ihttpmodule... lot of energy spent with poor result.
Any help warmly welcome,
Igor
I'm intercepting http requests coming to my asp.net application in order to
do some additional processing of html pages.
I'm having problems to access my variables stored in Session Object, that
always has IsSessionNew = TRUE. I can not figure out why is that. I expect
to have Session access in "Public Sub ProcessRequest(ByVal context As
HttpContext)" event. Is this correct? Or maybe to early/late? Of course I'm
using IRequireSessionState or IReadOnlySessionState, however none of this
work.
From the other side, SessionID inside of this session object seems to be ok,
it coresponds to ID stored in the cookie that I see
(context.Request.Cookies("ASP.NET_SessionId"). Is there a way to 'remind'
session object that it's instance is already alive on webserver?
So far I checked my web.config, IIS settings, I was experimenting with
global.asax events, ihttpmodule... lot of energy spent with poor result.
Any help warmly welcome,
Igor