What you may need to do to make sure that each of your applications use
different/unique cookie values is to modify your Application.cfm files to
include the following code after the CFAPPLICATION tag:
<CFIF IsDefined("COOKIE.CFID") AND IsDefined("COOKIE.CFTOKEN")>
<CFCOOKIE NAME="CFID" VALUE="#COOKIE.CFID#" EXPIRES="NEVER"
PATH="/myapp">
<CFCOOKIE NAME="CFTOKEN" VALUE="#COOKIE.CFTOKEN#" EXPIRES="NEVER"
PATH="/myapp">
</CFIF>
You'd have to change the value of the PATH attribute for each of your sites.
The above code essentially rewrites the cookies set by ColdFusion so that
they retain the same value but are reset to only apply to the appropriate
application/subdirectory.
--
Mosh Teitelbaum
evoch, LLC
Tel: (301) 942-5378
Fax: (301) 933-3651
Email: [EMAIL PROTECTED]
WWW: http://www.evoch.com/
-----Original Message-----
From: Jim McAtee [mailto:[EMAIL PROTECTED]
Sent: Friday, January 23, 2004 6:10 PM
To: CF-Talk
Subject: Re: CF Client Cookies
Thanks. I thought that might be the meaning of path in the cookie, but the
implication (if any) for CF applications is still unclear to me.
I notice that in CF5, the CFCOOKIE tag permits you to specify a path, while
CFAPPLICATION does not. It would seem that if you've a application.cfm file
located in a certain subdirectory (in relationship to the site root), that
you might want to set the path to that subdirectly. But again, I don't
fully
understand the implications of path or its affect when you have multiple cf
apps residing on the same site where CF sets path=/ for all its client
cookies.
----- Original Message -----
From: "Mosh Teitelbaum" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Friday, January 23, 2004 12:51 PM
Subject: RE: CF Client Cookies
> Jim:
>
> The path attribute specifies the URL within a domain to which the cookie
> applies. It's a means of saying something like "this cookie only applies
to
> resources located in/under the following directory."
>
> In your case, it means that the cookies apply to the entire site.
>
> --
> Mosh Teitelbaum
> evoch, LLC
> Tel: (301) 942-5378
> Fax: (301) 933-3651
> Email: [EMAIL PROTECTED]
> WWW: http://www.evoch.com/
>
> -----Original Message-----
> From: Jim McAtee [mailto:[EMAIL PROTECTED]
> Sent: Friday, January 23, 2004 2:37 PM
> To: CF-Talk
> Subject: CF Client Cookies
>
>
> I've got an application that uses both CF client and session management.
> It's located in a branch off of the web site's root, while there are other
> branches and two more existing applications on this same site that utilize
> different cf application names:
>
> www.mysite.com
> /
> ../myapp
> ../old_app
> ../even_older_app
>
> I just noticed when examining a GET of http://www.mysite.com/myapp/ that
CF
> sets its client cookies as follows:
>
> Set-Cookie: CFID=2822204; expires=Sun, 27-Sep-2037 00:00:00 GMT; path=/;
> \r\n
> Set-Cookie: CFTOKEN=52387784; expires=Sun, 27-Sep-2037 00:00:00 GMT;
path=/;
> \r\n
>
> What exactly does the "path" component of the cookie designate? I'm
> wondering if there could potentially be a session conflict with the other
> applications running on the site.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
