Forum Moderators: open

Message Too Old, No Replies

session cookie question

session living time

         

Xuefer

8:04 am on Nov 12, 2003 (gmt 0)

10+ Year Member



start 1 IE process
suppose this window is "WinA"
open a site, got newly created session cookie
shift+click on a link(same domain) to open new window(same process different thread) as WinB
refresh WinA, cookie is ok
but after i close WinB, then refresh WinA, all session cookies is lost

('session' mentioned above is cookie without expire time, not server side session storage)

what on earth is that happening? is it correct behavior? any rfc/document?

Mr_Brutal

8:44 am on Nov 12, 2003 (gmt 0)

10+ Year Member



Hello,

I don't know if this is your problem or not but i made a mistake when using cookies and this is what they told me Thread [webmasterworld.com]

Hope this helps

Xuefer

10:45 am on Nov 12, 2003 (gmt 0)

10+ Year Member



smiliar to:
[support.microsoft.com...]

but i'm not using FILE://

Mr_Brutal

11:18 am on Nov 12, 2003 (gmt 0)

10+ Year Member



Again i don't know if this is what you are not doing, but your WinB will need to resave the cookie data before it is closed otherwise the cookie is lost, at least thats the impression i got from the other thread.

Does your WinB do that?

Xuefer

11:57 am on Nov 12, 2003 (gmt 0)

10+ Year Member



hrm..
why resave? WinB is same domain as WinA but different url.
WinA is always keep open just refresh after WinB is closed.
Its session cookie shouldn't be lost

Mr_Brutal

12:15 pm on Nov 12, 2003 (gmt 0)

10+ Year Member



My problem was that i was only saving a single key data in the cookie on my equivelent of WinB, and this meant i lost all my other cookie data - until i changed it to resave all the keys in the cookie.

Sorry i thought it was clear from the thread above what my problem had been and the solution, if its not what is happening for you then i can't help you much more really as am not a cookie expert just a cookie user.

Sorry

Xuefer

2:09 pm on Nov 16, 2003 (gmt 0)

10+ Year Member



seems it's only me have this problem
tested on other computer on same site using same system same browser version, no such error