I had the exact same problem this week when I upgraded my ie6 with the newest M$ patches.
I have a form, which sends a login page to a script. Because the login page uses a submit button, the cookies for CFID and CFTOKEN would normally be set there. After processing, the login script cflocations the person to a new page. The funny thing is that I am not using CFLocation, but the Fusebox CF_Location tag which was not cookie problematic. The app works fine on Opera, Netscape 4.x and 6.2 as well as on IE < 6. The application was definitely losing cookies, I cfdumped all session variables and http_cookie changed each time. My ultimate solution was to pass (during the first CF_Location only), the CFID and CFTOKEN on the URL. After that I don't pass them and the application works fine. I checked all my settings in IE 6 and they were all accepting cookies. Very weird. Any other better solutions (or even better rational explanations for the problem) would be much appreciated. Sandy Clark -----Original Message----- From: Kym Kovan [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 28, 2002 8:14 PM To: CF-Talk Subject: Re: Big problem- session vars not saved in IE6 on CF5 Hi Don, >I am having a big problem with an old standard login system. This is the >most simple login system I know and have used it for years. > >It consists of: >Login form page >Login action page >Main page >Session variables tracking who is logged in > >The user enters in their login acct, the action page compares it against the >db, then sets some session variables and uses cflocation to forward them to >a new page or back to the login page if they fail. The application page >checks for the session variable to see if they're logged in and uses >cflocation to send them back to the login page if the var doesn't exist. I am slightly surprised that this has ever worked if I understand it correctly. Session and Client variables normally use cookies to control themselves, if not you have to use CFID and CFToken in your URLs. cflocation has a proviso that if you use it then any cookies set in the page before the cflocation tag will _not_ actually get sent to the browser under normal circumstances. This means that if you have a cflocation in your initial entry then your session may not well be set up properly..... -- Yours, Kym ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
