Forum Discussion
DaveC_53879
Aug 17, 2011Nimbostratus
Thanks for the responses. I had actually tried using a named cookie yesterday but got some strange results and I get the same strange results today, but now I see where the problem is. I've been using IE8 and FF4 to test. IE8 is now working correctly, as it is inserting the correct domain name in the cookie and so stays persistent regardless of the sub-domain. Thanks for the help getting this working. I see the same results in FF 3.6.17.
FF4, on the other hand, stays persistent for all sub-domains, but it does not show a cookie, and nothing is logged, but hitting F5 to refresh the page switches it to the next available server, then loads the cookie, stays persistent to the new server and the F5 logs the activity. This is what I was seeing yesterday and what was throwing me off. I upgraded to FF 6.0.1 and see the same behavior. I assume these new versions of FF will behave the same way for exisitng sites using a similar rule. Clearing the cache in FF 4 and 6 fixed this behavior, but the default settings are to cache sites and the only way I see to stop that is to set the cache to zero bytes, which most users are not going to do. There is no need to clear the cache in IE8 or FF3. Removing cookies before-hand didn't make any difference.
Has anyone else seen this? Thanks again.