LiveDocs Comments - coldfusion - 6.1 - htmldocs - tags-a18.htm

coldfusion/6.1/htmldocs/tags-a18.htm

marnen — 2006-02-16T07:57:30

Actually, the spec *does* specify that many periods. Quote:
> Only hosts within the specified domain can set a cookie for a domain and domains must have at least two (2) or three (3) periods in them to prevent domains of the form: ".com", ".edu", and "va.us". <

coldfusion/6.1/htmldocs/tags-a18.htm

ptyng — 2005-05-04T12:20:59

There is nothing in that spec about requiring domain when a path is required or leading periods. They even give examples with paths and no domain specified. Perhaps Macromedia needs to re-read the spec and conform to it in addition to just saying they do.

coldfusion/6.1/htmldocs/tags-a18.htm

xigarete — 2005-02-23T17:59:12

1) CF filenames are case sensitive in *nix, but almost nothing else is

2) There should be a way to explicitly set a cookie to session (instead of implicitly by not setting that variable) You'd want to do this if you were writing a flexible function that used this and might set session and nonsession cookies.

coldfusion/6.1/htmldocs/tags-a18.htm

vadtec — 2005-01-16T19:13:38

These LiveDocs should really include information on variable naming on *nix OSes. For instance, is it COOKIE.whatever, cookie.whatever, Cookie.whatever, or is it cOoKiE.whatever? For *nix OSes, this is usually a big deal, because they are case-sensetive. Winblows could care less (but then again Winblows sucks) but unfortunately MicroShaft has the market for ColdFusion "ease-of-use". If there is a *nix version of these LiveDocs, please tell me where it is and re-organize macromedia.com to be more friendly to the *nix community. Don't just offer a *nix version and then have nothing but Winblows documentaion (for the most part).

coldfusion/6.1/htmldocs/tags-a18.htm

monochrome_jason — 2004-12-08T02:37:48

>>
erm thats going to throw an error

or

coldfusion/6.1/htmldocs/tags-a18.htm

halL — 2004-12-03T12:02:01

The ColdFusion cfcookie tag conforms to the requirements of the Netscape cookie specification, which requires a domain name and specifies that the domain name have at least two or three periods.
For the cookie specification, see http://wp.netscape.com/newsref/std/cookie_spec.html.

coldfusion/6.1/htmldocs/tags-a18.htm

MarkZet — 2004-12-02T01:05:55

Our intranet server is accessed through its netbios name, which does not contain two dots (the minimum amount that is required by Internet Explorer when setting a domain cookie). Therefore, we cannot set a cookie for the intranet with a path using the CFCOOKIE tag.
A workaround for this issue:
name="Set-Cookie"
value="COOKIENAME=val;path=/test/;expires=#GetHttpTimeString(dExpiryDate)#">

Why is it that the domain is necessary when specifying a path?

coldfusion/6.1/htmldocs/tags-a18.htm

2004-11-30T09:45:58

I am unable to get the expiration parameter to work with anything but a number of days (i.e. expires="1"). I need the cookie to expire 4 hours from the time it is created. I have tried both creating a datetime object at runtime and hardcoding a date/time (i.e. 12-01-2004 00:00:00). In both cases the cookie is created but expires as soon as the browser is closed.