LiveDocs Comments - coldfusion - 6 - CFML_Reference - Tags-pt119.htm

coldfusion/6/CFML_Reference/Tags-pt119.htm

istvanb — 2006-01-22T20:11:50

In addition to sdwebguy99's comment:
I set a cookie (with cfcookie) originally with the domain defined as "domain.com" - without "www.", so it works accross subdomains - but after trying to alter the cookie's value using cfset,instead of modifying the existing cookie, a new cookie was created with the same name, but with the domain "www.domain.com". (This is on CFMX 6.1)

coldfusion/6/CFML_Reference/Tags-pt119.htm

sdwebguy99 — 2004-10-29T16:09:28

Something I have noticed. I use CFCOOKIE to set the cookie with an expires date of 20 years. Later in my app, I update the value of the cookie by using CFSET COOKIE.COOKIENAME = VALUE. Because I have cookie notification turned on, I see that the expires date of the new cookie is end of session. We are running CFMX 6.1 (no updater). Is this a known issue?

coldfusion/6/CFML_Reference/Tags-pt119.htm

2004-08-04T12:22:43

The documentation never tells you how to change the value of a cookie, leaving it for everyone to figure out; here's how i finally figured it.

coldfusion/6/CFML_Reference/Tags-pt119.htm

spage-mm — 2003-05-02T02:53:00

Couple of things I've noticed:

1. always creates an uppercase cookie name. CF is case-insensitive so if you set and read cookies only in CF you'll never notice. But if other server code sets a lower- or mixed-case cookie, CF's Cookie scope will only report one of the values, and you can't update the lowercase cookie from CFMX unless you use

2. If other code sets a cookie to a value with a comma in it and doesn't URL-encode it, CF gets very confused and only returns the part of the value in front of the comma. According to Netscape's original vague cookie spec you shouldn't have funny characters like commas in the cookie name-value pair, but not everyone obeys the spec. CF encodes and decodes funny characters in cookies that it sets and read.

coldfusion/6/CFML_Reference/Tags-pt119.htm

wickedXen — 2003-01-13T03:24:00

oh... and BTW... I thought this documentation was gonna be updated... I'd like to see some examples and expanded discussion on the path and domain attributes and their effects. It would be even better if the docs in dwmx were atleast as complete as these... maybe even a livedox xml feed to dwmx 6.2? Oops sorry... This should be requested elsewhere. Sorry ;)

wickedXen

coldfusion/6/CFML_Reference/Tags-pt119.htm

wickedXen — 2003-01-13T03:20:00

Mr. Gilson...
All other Macromedia Documentation dictates that it isn't set, and so does experience. is suggested for a good reason. :)

wickedXen
cfDev since dateformat(dateAdd("yyyy", -7, now()),"yyyy");

coldfusion/6/CFML_Reference/Tags-pt119.htm

sgilson102 — 2002-08-12T21:26:00

Macromedia Update:

The documentation incorrectly states that creating a new cookie using cfcookie on the same page you use cflocation would result in the cookie not being created. The cookie will be created.

Stephen M. Gilson
Macromedia

coldfusion/6/CFML_Reference/Tags-pt119.htm

ctina — 2002-07-19T19:19:00

Update from Macromedia, in response to anandasim, re cfcookie, getting a cokie value: thanks for your comment. We'll update the documentation to include more information.

coldfusion/6/CFML_Reference/Tags-pt119.htm

ctina — 2002-07-11T20:14:00

Update from Macromedia: The CFCOOKIE EXPIRES = "NEVER" option causes the cookie to expire 30 years after the current date.

coldfusion/6/CFML_Reference/Tags-pt119.htm

h2oman — 2002-06-27T17:26:00

use the following cookies to force sessions to expire a session @ browser close, instead of letting the cookies persist for the length of the session timeout.

coldfusion/6/CFML_Reference/Tags-pt119.htm

anandasim — 2002-06-23T21:38:00

cfcookie documentation is very sparse about how to retrieve the cookie value.

Had to read over and over again and then see that the cookie valie is Cookie.var1