The 2 extra lines of code doesn't really amount to much trouble but you are
correct, there is more than one way to solve the problem. I've always
preferred setting the cookies manually to make sure it's done correctly.
-Cameron
-----------------
Cameron Childress
Sumo Consulting Inc.
---
cell: 678.637.5072
land: 858.509.3098
aim: cameroncf
email: [EMAIL PROTECTED]
-----Original Message-----
From: Dave Carabetta [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 01, 2004 7:50 PM
To: CF-Talk
Subject: Re: Maintain sessions/clients across domains.
> This should do it...
>
> <cfapplication
> name="loginApp"
> clientmanagement="yes"
> clientstorage="bww"
> setclientcookies="no">
> <cfcookie name="CFID" value="#client.CFID#" domain=".whatever.com">
> <cfcookie name="CFTOKEN" value="#client.CFTOKEN#" domain=".whatever.com">
>
> Tell CF NOT to set the cookies automatically (because you're doing it),
and
> then uses the domain attribute of the cfcookie tag to tell the browser
this
> cookie should be sent to all subdomains for your site...
>
Why go through that trouble? Why not just use the setDomainCookies attribute
of the cfapplication tag to "yes"? That effectively does what you're doing
above (sets the cookie as domain.com instead of www.domain.com) and you
don't have to resort to a quasi-hack like you use above. Don't
misunderstand, it's not that your way doesn't work, it's just that there's a
"built-in" way to do it. You may also want to check the recent hotfix that
was released regarding domain cookies too if you're using MX 6.1.
Regards,
Dave.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
