> How in the world do you keep a session alive in CFMX when...
> 
> A) Cookies are disabled
> 
> and
> 
> B) You move from one domain to the other
>
> I have 3 situations with my shopping cart.
> 
> 1) When a person has cookies disabled I add cfid and cftoken 
> to the URL. This has worked fine to keep the session alive 
> since 4.01.
> 
> 2) When a person clicks checkout, I change the URL to the 
> secure URL and add cfid and cftoken to the URL. Since it goes 
> to a page under the same cfapplication tag with the same 
> application name, the session stays alive, since 4.01.
> 
> However, neither of these work in CFMX. HOW do I keep a 
> session alive under these 2 conditions. It shouldn't be 
> brain surgery. One thing I HAVE noticed is that sometimes 
> there is a JSESSIONID cookie set. So I passed that value 
> in the query string also, but to no avail.
> 
> 3) Occasionally, on a redirect, I get that nasty, UGLY 
> JSESSIONID URL parameter. I say UGLY, because it doesn't 
> create a query string. It makes it like...
> 
> www.domain.com/page.cfm;JSESSIONID=987908979808758
> 
> WHAT is that and HOW can I make it stay away?

That's the J2EE session ID. You can use J2EE sessions and session IDs
instead of "traditional" CF session IDs (CFID & CFTOKEN). There's an option
in the CF Administrator to enable this. You might want to turn this off; if
you do, I'd expect everything to just work fine for you.

Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription: 
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm

                                Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
                                

Reply via email to