| 12:49 am on May 20, 2004 (gmt 0)|
You might want to check your server's cache-control headers for those images... Or preload the images to prevent this from happening with other 'playful' users.
There were some threads here a while back discussing problems with IE and rollover images reloading from the server -- you might want to try searching for them.
| 1:11 am on May 20, 2004 (gmt 0)|
But how do I "check your server's cache-control headers for those images"?
Also, these images are preloaded.
I will search on [IE rollover images reloading] now
| 1:20 am on May 20, 2004 (gmt 0)|
Try this Server Headers checker [webmasterworld.com].
| 1:33 am on May 20, 2004 (gmt 0)|
HTTP/1.1 200 OK
Date: Thu, 20 May 2004 01:30:52 GMT
Server: Apache/1.3.27 (Unix) DAV/1.0.3 mod_gzip/22.214.171.124a mod_ssl/2.8.10 OpenSSL/0.9.6c PHP/4.3.5
Last-Modified: Fri, 14 May 2004 11:50:28 GMT
Keep-Alive: timeout=15, max=100
is it the Keep-Alive causing the problem?
| 3:06 am on May 20, 2004 (gmt 0)|
No, you have no Expires or Max-age info for cache control [mnot.net] there... Therefore, it is up to the intervening caches and the browser cache to decide when the files are stale and need to be re-fetched.
This is usually not the problem. A too-short expiry period or an incorrectly-specified cache-control header can cause your problem, but usually missing cache-control header info causes stale-content problems -- stuff is not re-fetched often enough.
Look into the IE image caching bug [webmasterworld.com] I mentioned, and as additional data, see what happens if you visit your site with a Mozilla browser and "play" repeatedly with the mouseover images. If you see the same problem with Mozilla/Netscape/FireFox in your access logs, it's not an IE bug, it's site-related.