My inclination is that HTTPS and HTTP are considered 'seperate' domains.
I would consider tracking down why the user is being switched back and
forth, and if possible keep them in one place.
Calvin
- Original Message -
From: John Paul Ashenfelter [EMAIL PROTECTED]
To: CF-Talk [EMAIL
From: Calvin Ward [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Wednesday, May 28, 2003 11:58 AM
Subject: Re: Client variables and SSL problem
My inclination is that HTTPS and HTTP are considered 'seperate' domains.
I would consider tracking down why the user is being switched back
As you know, client variables are keyed off of cfid and cftoken which MUST
be passed via cookie or url in order to maintain state. What you might not
know is that client variables are also keyed off of the application name (as
specified in cfapplication...). Make sure the application name is the
Ashenfelter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 28, 2003 10:54 AM
To: CF-Talk
Subject: Re: Client variables and SSL problem
From: Calvin Ward [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Wednesday, May 28, 2003 11:58 AM
Subject: Re: Client variables and SSL problem
- Original Message -
From: Bryan Love [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Wednesday, May 28, 2003 3:18 PM
Subject: RE: Client variables and SSL problem
As you know, client variables are keyed off of cfid and cftoken which MUST
be passed via cookie or url in order
- Original Message -
From: Andre Turrettini [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Wednesday, May 28, 2003 3:33 PM
Subject: RE: Client variables and SSL problem
you might try appending the cfidtoken to the url on the links that move to
ssl. This would only fix
6 matches
Mail list logo
