Originally posted by chanoch wiggers:
why cant you use encode URL? (...) like
var think = "<%=encodeURL("/")%>";
or something
Well, either you don't understand the problem or i don't see the solution... I don't believe that Explorer would act different just because of using a string-to-string function in my code.
However, i walked around the problem in the past few hours and i found that if i open a simple window when my program starts (and ask user not to close it, for a whatever reason), this solves the Whole Big Explorer 6 Problem (aka WBE6P from now on
) So this is a quick patch until ms comes out with the bugfix. Basically, the cookie problem happens when you close the LAST window that has been window.open()-ed by your site. If one of them stays, your session parameters stay too.
There are a few cases when Explorer doesn't lose the cookie but these are more like accidents. Normally it does. This is a documented bug, see
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q315713 for details. BUT DON'T THINK IT'S OKAY if you download the browseui.dll mentioned on this page - i got that 1024512 bytes long version and it does NOT solve the problem. What you really can do is 2 easy-to-follow steps: sit and wait
(any other patch or solution or workaround or whatever would be still appreciated! thx)