If your Application has setclientcookies=yes, which is the default, a
cookie/session will be created for each host used by the client to access
the site.
So
domain.com,
www.domain.com, 127.0.0.1, could all be the same physical web
site, but would have 3 different cookies and sessions generated.
You mentioned you setup a redirect to www. If the redirect is done via
cflocation, then you would still see 2 CF cookies at the client, since the
client actually is hitting both host names. A web server redirect would
resolve this, so the client never really gets to
domain.com as a CF
request, hence no cfid/cftoken cookie.
Another common issue I have seen is a login session occurring under www,
but somewhere in the application a link goes to the non www host, which
could result in a dropped session/login depending on how things are coded.
Byron Mann
Lead Engineer & Architect
HostMySite.com
Archive:
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:359385