You should use DOMAIN=".rudy.ca", which will set a cookie that can be read by any server in the rudy.ca domain. If you start the DOMAIN with a dot, it acts as though there is a wildcard preceding that first dot. Chris Evans chris at fuseware.com http://www.fuseware.com -----Original Message----- From: thelist-admin at lists.evolt.org [mailto:thelist-admin at lists.evolt.org]On Behalf Of rudy Sent: Tuesday, July 24, 2001 11:53 AM To: evolt thelist Subject: [thelist] cold fusion cookie question working my way through my first cookie application, i came across the following gem in the cold fusion docs -- DOMAIN Specifies the domain for which the cookie is valid and to which the cookie content can be sent. An explicitly specified domain must always start with a dot. This can be a subdomain, in which case the valid domains will be any domain names ending in this string. For domain names ending in country codes (such as .jp, .us), the subdomain specification must contain at least three periods, for example, .mongo.stateu.us. In the case of special top level domains, only two periods are needed, as in .allaire.com. so, my domain is rudy.ca -- what am i supposed to stick in front of that? if i use DOMAIN=".www.rudy.ca" does that mean the cookie won't work if people are surfing to http://rudy.ca pages? will i be forced to use that horrible www thing? that sucks, big time what if i say DOMAIN="..rudy.ca" (i.e. three dots, but no subdomain)? my application isn't far enough along to test yet, so i thought i'd ask and what makes dot-com so special, anyhow? rudy --------------------------------------- For unsubscribe and other options, including the Tip Harvester and archive of TheList go to: http://lists.evolt.org Workers of the Web, evolt !