Hi Ben,
Thanks for posting here. I'm glad that you've figured out this problem
yourself. As you've found , the session (on the serverside) is associated
with client via a cookie variable named "ASP.NET_SessionId". If we want to
mantain the session outside , not via asp.net page request, we need to
manually retrieve the cookie variable from cookie collection and repost it
next time so as to maintain the association. In addition, as the other
customer has mentioned, if
the client doesn't support cookie, the ASP.NET serverside also provide a
cookie less session implmentation , which will put the session id as
encryped value in the url, thus, we can't use cookie variable to retrieve
the sessoinid. For detailed info on the ASP.NET session implemention, you
can view the following reference in MSDN:
#Underpinnings of the Session State Implementation in ASP.NET
http://msdn.microsoft.com/library/en-us/dnaspp/html/aspnetsessionstate.asp?f
rame=true
Also, here is a tech ariticle discussing the cookie in ASP.NET
#basics of cookies in asp.net
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vstechar
t/html/vbtchaspnetcookies101.asp
Hope they're also helpful to you.
Regards,
Steven Cheng
Microsoft Online Support
Get Secure!
www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
Get Preview at ASP.NET whidbey
http://msdn.microsoft.com/asp.net/whidbey/default.aspx