I have an issue with IE7 not responding as it should after a log-in to a website I built for a client. This same problem also affects the add to basket or add to wish-list functionality, the checkout process, and all other Ajax requests. Here is a breakdown of what happens...
1. User clicks on the "log-in" link. 2. Log-in page opens (new page). 3. User logs in (Ajax submission of credentials, page supposed to reload, but does not in IE7) 4. Log-in block is supposed to show user details now, but does not, because page did not refresh. 5. User presses Control+F5, and page now shows user logged in.
Now the user continues...
1. User adds item to basket (ajax request firing, and popup says "added to basket" but basket is not refreshed. 2. User presses Control+F5, basket is refreshed.
So, as far as I can tell, this seems to be sessions/ajax related, but I am not sure where to check - this works wonderfully well for all browsers except IE7.
Using Fiddler, I see nothing out of the ordinary - the scripts are fire as they should be, session IDs are not overwritten, but somehow the Ajax requests simply does not refresh the elements they are supposed to. Only after pressing Control+F5 does it work. The HTTP headers return 200, not 304 so I don't think it is a caching issue in the script - perhaps a caching issue in the client's browser or client's network settings?
Further testing indicates that even though the header returns 200, the script fires "too fast" it sends an HTTP/200 header, but does not actually run (I made an alert to popup if you click the add to cart button) and the alert more often does not display than it does. It displays around once every 15 times or so. Very weird...
Now - this sometimes happens, and sometimes not, more often not.
Our internet connection is very slow today. Perhaps this is related? I figured (it seems like) FF just waits long enough for a response, and IE7 does not. Perhaps it is related to our internet connectivity? Client and I are not using same ISP, but what we do have in common is the same telecoms provider Telkom (affectionately known as Hellkom in South Africa) and the hosted server. The server is hosted at the data center of a large cellular provider in South Africa, but I believe Telkom still does the "last mile" of all internet traffic in South Africa (unless I missed the lifting of this historic change in SA democracy).
So - the social.msdn forums are getting somewhere with this problems - various MVP's browsing my topic and giving hints to try and test. I will provide some information here if the problem gets solved, for other interested parties.