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]
