Try this if you want to see if the session has expired. I forgot where I
found this but I thank them just the same!
private void CheckForSessionTimeout(){
if (Context.Session != null){
if (Session.IsNewSession){
string szCookieHeader = Request.Headers["Cookie"];
if ((null != szCookieHeader) &&
(szCookieHeader.IndexOf("ASP.NET_SessionId") >= 0)){
Response.Redirect(this.ResolveUrl("~/sessionTimeout.aspx"));
}
}
}
}
--
Ian
"tom pester" wrote:
They are independant. The only thing that fiddles with the referrer is the
use who may choose to hide it for privacy reasons.
BTW In the HTTP Standard (at a code-level) referrer is misspelt: 'referer'.
Cheers,
Tom Pester
Thanks, Any other comments from any one else.
-Smith
"Jon" <ru******@msn.com> wrote in message
news:%2***************@TK2MSFTNGP14.phx.gbl... That property is independent of the session as far as I know.
"Peter Smith" <Pe*********@hotmail.com> wrote in message
news:Om**************@TK2MSFTNGP15.phx.gbl...
Will the below statement returns TRUE or FALSE iif the session is
expired?
(Request.UrlReferrer) Is Nothing
I am using ASP.Net 1.1 and IIS 5.0.
Thanks,
Smith
