Re: session question
From: Patrick Y. Ng \(ms\) (patng@microsoft.com)
Date: 07/23/02
- Next message: San: "Re: session question"
- Previous message: San: "session question"
- In reply to: San: "session question"
- Next in thread: San: "Re: session question"
- Reply: San: "Re: session question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Patrick Y. Ng \(ms\)" <patng@microsoft.com> Date: Mon, 22 Jul 2002 15:49:18 -0700
(a) It's because no expiration date is set on the session id cookie
(b) Session expiry isn't implemented using the cookie expiry. It's
implemented on the server side. (Consider the case where cookieless is
used) Session.Timeout gives you the expiry period in minutes.
-- Patrick Y. Ng ASP.NET Developer This posting is provided “AS IS” with no warranties, and confers no rights. "San" <sanjay_nadimpalli@yahoo.com> wrote in message news:eRpWvpcMCHA.668@tkmsftngp09... > I have the following two lines of code that get called on every http > request: > > HttpCookie cookie = > HttpContext.Current.Request.Cookies["ASP.NET_SessionId"]; > > Response.AppendToLog("Cookie expires on date:" + cookie.Expires); > > The expiration time on cookie ASP.NET_SessionId is always January 1, 0001, > 12 AM. Two things: > > (a) Why is it initialized to Jan 1, 2001 12 AM? > > (b) Shouldnt the cookie expiration change whenever the user makes a request > (within the 20 minute interval, assuming session timeout is set to 20 > minutes). > > Thanks > > San > > > >
- Next message: San: "Re: session question"
- Previous message: San: "session question"
- In reply to: San: "session question"
- Next in thread: San: "Re: session question"
- Reply: San: "Re: session question"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|