cookie monster…
long time, no post… geez, well again busy at work and home… a stupid cookie issue arose with our product and windows nt 4.0. i couldn’t track the real problem down after several days of testing, installs, google and microsoft searches, but i was able to put a patch in place. kudos from the boss was nice, but i hate not having a true solution.
the problem was that ie 5.5 on nt 4.0 was loosing it’s cookies (tossing it’s cookies?) when we open a new browser window. i know that windows creates new processes for new windows in ie (if you’ve got more than 32 megs of ram installed) and we had issues several years ago with ie 4 and nt 4.0 with new windows… but i could not duplicate the problem at all! so frustrating! i put a patch in to pass the data via the url instead of a cookie and that works, but i wish i knew the combo to duplicate the problem. cookies aren’t really any more secure than url params if you’ve got a sniffer anyway, but it was a cleaner implementation. we’ll have to see what works in the long run.