No, my httpModule doesn't implement IRequireSession State.
The more I test it, the more I think it is not the problem with my
httpModule. Because at last, here's how I tested for the SessionID using a
normal ASPX page.
Sub Page_Load()
Response.Write( Session.Session ID.ToString())
End Sub
and everytime I refresh it, I get a new value! In the web.config file I have
<sessionState timeout="20" /> and still generating new SessionID on each
refresh.
The strange thing is that I have about 5 ASP.NET web sites currently running
and I tested on all of those websites. The result is surprisingly the Same!
How could a new SessionID be generated on each refresh????
I am absolutely hitting my head against the wall! Help!
MK
"John Saunders" <johnwsaundersi ii at hotmail.com> wrote in message
news:OU******** ******@TK2MSFTN GP09.phx.gbl...
"Mike Kline" <mk@nnnnnnnnnzz zzzzzzzzzzzzzzz zzzzz.zero> wrote in message
news:%2******** ********@TK2MSF TNGP14.phx.gbl. .. Hi There!
I'm creating a HttpModule and after AcquireRequestS tate event, I tried to
access the HttpApplication .Session.Sessio nID and somehow I'm getting a
new
value on every Refersh of ASPX page.
I thought SessionID is supposed to stay static until the session timeout
defined in the web.config. Or am I missing something here???
Does your HttpModule implement IRequireSession State?
I've seen this happen for pages which refer to SessionID but which do not
read or set Session.
John Saunders