Has anyone done work to figure out what exactly each of the cookies is for?
JSESSIONID=HEXSTRING
TRIBE_STATE=vtype=t|visitor=TRIBE-STYLE-ID
TRIBE_NET=6
TRIBE_TOKEN=MAYBEBASE64
remember=true
backtrack=closed
Remember is obvious, that's the 'remember me' checkbox at login. What about TRIBE_NET? Is that the locality you are in? And backtrack?
Are all three of JSESSIONID, TRIBE_STATE, and TRIBE_TOKEN needed? Or is one, perhaps TRIBE_TOKEN, a password used to recreate the others after a session timeout?
JSESSIONID=HEXSTRING
TRIBE_STATE=vtype=t|visitor=TRIBE-STYLE-ID
TRIBE_NET=6
TRIBE_TOKEN=MAYBEBASE64
remember=true
backtrack=closed
Remember is obvious, that's the 'remember me' checkbox at login. What about TRIBE_NET? Is that the locality you are in? And backtrack?
Are all three of JSESSIONID, TRIBE_STATE, and TRIBE_TOKEN needed? Or is one, perhaps TRIBE_TOKEN, a password used to recreate the others after a session timeout?
-
Re: the various cookies
Wed, October 20, 2004 - 11:58 PMbacktrack is the history tool. so i guess this remembers the status of your history widget.
jsessionid is the cookie JSP and servlets use to remember your current session
tribe_state seems to be more application specific holding several fields: cr, vtype, region (not the same as the r get param),visitor (not your person ID)
tribe_net (mine was 6) no idea what this would be, maybe related to load balancing?
tribe_token might be related to the remember me function as it's the only other cookie that doesnt expire at end of session. -
-
Re: the various cookies
Thu, October 21, 2004 - 10:59 AM"tribe_token might be related to the remember me function as it's the only other cookie that doesnt expire at end of session."
Must be it then. The base64 look of the value makes me think MD5, and if it is supposed to be persistent that would make sense as an identifying and authorization token. I didn't look at the longevity of the cookies when I inspected them.
Damn, I want a cookie editor for Firefox. Editing this stuff with proxies is such a chore.
-