I don't know if I'd call the jsessionid a "remnant" so much as a feature, and yes, of J2EE more than JRun itself. :-) As far as I can recall, one would have the same on Tomcat, WebLogic, etc. as (again, I think) it's the J2EE spec way of doing session id cookies. (As most here may already know, CF uses that if one enables "j2ee sessions" in the CF Admin, to cause use of JRun's underlying session mgt vs CF's.)
In mentioning Railo, MrB, I'm curious if there's something particular that you're thinking of that differs. Or was this just more of a "maybe it's different on Railo" kind of suggestion :-) Great stuff on the jrun-web.xml config. I recall seeing that in the past but had forgotten about it myself. /charlie From: cfaussie@googlegroups.com [mailto:cfaus...@googlegroups.com] On Behalf Of MrBuzzy Sent: Monday, December 06, 2010 9:02 PM To: cfaussie@googlegroups.com Subject: Re: [cfaussie] Re: Handling sessions across subdomains Hi Peter, I did a bit more investigationing :) To recap, your problem is twofold; 1. You'll need session replication between CF instances 2. You need to force the jsessionid to be a domain cookie Session replication can be annoying. But not impossible. You might need to consider running your login page in the same CF instance as the blogs (sub domains). Or re architect it so the login state is stored in the cookie scope instead of session. Or consider a single sign on mechanism. Or use Railo ;) The jsessionid is an artifact of JRun (J2EE really), intercepting or rewriting it using CF will also be a bit hacky and problematic. Instead you can force JRun to set a domain cookie, as follows; <snip> -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaus...@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
