In this case, the default client variable storage was set to the Registry. The reason
CF
was generating a new CFID/CFTOKEN in the cookie despite passing them in a URLwas
apparently related to passing the CFID/CFTOKEN in a search-engine-friendly slash
delimited way, e.g., CFID/xxxx/CFTOKEN/xxxxxxxx, even when the user had cookies turned
on. I discovered my frustrating problem of session failure disappeared if I reverted
to
the standard query string, OR if I added some code that only added the slash-delimited
CFID/CFTOKEN info when the user had cookies turned off.
I'm still not sure why the slash-delimited CFID/CFTOKEN caused a problem. My
guess is that CF scans the query strings for a normal-looking CFID=xxx&CFTOKEN=xxxxxx
and it didn't recognize CFID/xxx/CFTOKEN/xxxxxx even though my code set URL variables
based on a parsing of the slash-delimited string.
(Thanks for your response, Jennifer -- never received your earlier posting...)
> >What might cause CF to generate a new CFID/CFTOKEN pair in the HTTP_Cookie
> >even when I'm
> >passing them in a URL?
Jennifer <[EMAIL PROTECTED]> wrote:
> If you have the default client variable storage in the variables section of
> the server administrator set to store in cookies instead of the registry.
Gene Kraybill
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
