What's worse is that if the cookie is blank, it creatse a session with a blank CFID/CFTOKEN pair.� What this means is that in testing, we had the entire company using one session (as we all had CFID/CFTOKEN cookies that were blank).� This seems like a pretty serious bug at least.
You could switch to J2EE Session Variables which would stop the app being confused by CFID / CFTOKEN (since it would ignore them). Also the jsessionid cookie is browser-based, not disk-based so it doesn't persist.
Regards, Sean
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
