Question
CFMX7 and session cookies- broken/different?
Howdy,
We've migrated a site from CFMX 6 to CFMX7(Linux in both cases), and we are finding users seem to be having a hard time holding on to their sessions. Our client is getting a lot of complaints that users have to adjust their cookie acceptance policies, and that they buy from other sites off the web and don't have a problem. So our client is coming back to us for answers, and so far we don't have any. The issue seems primarily, but not exclusively, confined to IE. Compounding the issue is that we do not seem able to reproduce the problem, but by logging the CFID and CFTOKEN cookies on incoming requests, we can see that a lot of people out there are having issues (the CFID and CFTOKEN cookies are not returned in their requests, and when we trap their SESSION.CFID AND SESSION.CFTOKEN values, it changes on every page hit). Right now, we see about 100-150 incidents a day.
At this point it seems clear there is a difference, although precisely what that difference might be is unclear. We've picked up all the hot fixes and we are running 7.0.2 now, but it seems to make no difference. We can try to provide support and workarounds for users to adjust their cookie acceptance policiies, but not everyone can follow instructions, and why should they have to- if they've bought from a site before, why can't they buy now?
In our application.cfm, client management is set to No, and sessionmanagement, setclientcookies, and setdomaincookies are all set to yes; this worked fine before, and also matches another 6.1 Linux site that seems to be burbling along perfectly fine.
All of these sites are e-commerce, so we do not have direct contact with the customers, just our (increasingly annoyed) client.
If we can't get this solved, we may have to investigate other alternatives to CF- our clients don't want to have to deal with angry customers, or pay to have their sitre completely rewritten when moving to a new CF release.
Any ideas? We're logging what data we can from the CGI request, and tracking the cookies sent back to us through GetHttpRequest.
Than you for your time and attention
We've migrated a site from CFMX 6 to CFMX7(Linux in both cases), and we are finding users seem to be having a hard time holding on to their sessions. Our client is getting a lot of complaints that users have to adjust their cookie acceptance policies, and that they buy from other sites off the web and don't have a problem. So our client is coming back to us for answers, and so far we don't have any. The issue seems primarily, but not exclusively, confined to IE. Compounding the issue is that we do not seem able to reproduce the problem, but by logging the CFID and CFTOKEN cookies on incoming requests, we can see that a lot of people out there are having issues (the CFID and CFTOKEN cookies are not returned in their requests, and when we trap their SESSION.CFID AND SESSION.CFTOKEN values, it changes on every page hit). Right now, we see about 100-150 incidents a day.
At this point it seems clear there is a difference, although precisely what that difference might be is unclear. We've picked up all the hot fixes and we are running 7.0.2 now, but it seems to make no difference. We can try to provide support and workarounds for users to adjust their cookie acceptance policiies, but not everyone can follow instructions, and why should they have to- if they've bought from a site before, why can't they buy now?
In our application.cfm, client management is set to No, and sessionmanagement, setclientcookies, and setdomaincookies are all set to yes; this worked fine before, and also matches another 6.1 Linux site that seems to be burbling along perfectly fine.
All of these sites are e-commerce, so we do not have direct contact with the customers, just our (increasingly annoyed) client.
If we can't get this solved, we may have to investigate other alternatives to CF- our clients don't want to have to deal with angry customers, or pay to have their sitre completely rewritten when moving to a new CF release.
Any ideas? We're logging what data we can from the CGI request, and tracking the cookies sent back to us through GetHttpRequest.
Than you for your time and attention