Hi Bach, just wanted to chime in on your suggestion. I tried a similar IE 6 browser setup a year or so ago when testing one of our web apps. I noticed very strange behaviour that was directly traceable back to the Cookie settings. For our secure (https) web app, it was looking for some cookie information in the Cache rather than in memory for some of the pages. When it couldn't find it there, really strange things started happening in the application. Turning the cookies back on made the strange behaviour go away. After that test, our developers added a check for Cookies routine to keep us (testers, and users too) from doing it again. ;-)
Just thought I'd throw it out there that sometimes turning off all Cookies is not a viable solution. Cheers! Paul C. On 08/03/07, Bach Le <[EMAIL PROTECTED]> wrote:
Swarma, Actually, I believe keeping the cookies from writing to disk is a better solution than the one Paul is suggesting (using code to delete it). In IE7 (don't know about 6 but I think it is possible). In IE7, do the following: 1. Tools -> Internet Options 2. Click on the "Privacy" Tab 3. Click on the "Advanced" button 4. Check "Override automatic cookie handling" 5. Under First-Party Cookies, select "Block" 6. Under Third-Party Cookies, select "Block" 7. Check "Always allow session cookies" This will keep the cookies in memory for as long as the browser is open and clears them when the browser is closed. Cookies are never written to disk so the data does not persist across multiple IE processes.
_______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
