Hi Phil,� Thanks for your help.� It's been set to use jsessionids for over a year already and has been restarted numerous times and even moved servers recently. From what I understand, what is happening shouldn't be happening. It just doesn't make any sense to me that a) the CFID and CFTOKEN cookies are still being set (in addition to the session.sessionid) and b) the jsessionid cookie is not a domain cookie .. grrr .. I'm guessing the two are connected though. Might help in the hunt for a solution.� I might have to resort to setting my own cookie as you suggest though. I have played around with that and got it to work, but I'd rather use what *should* work out of the box in Coldfusion.� Cheers, Peter
You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/ |
- [cfaussie] Re: JSessionID and domain cookies Jason Sheedy
- [cfaussie] Re: JSessionID and domain cookies Phil Rasmussen
- [cfaussie] Re: JSessionID and domain cookies Peter Daams
- [cfaussie] Re: JSessionID and domain cookies Steve Onnis
