A lot of Linux + Apache servers will be CSS, JS and pictures of these static content settings cache, to IE here will be a local cache. So when we update the CSS file, there are often no updates from the client, causing the problem to appear. I've been using timestamp parameters to solve the problem before:
<link rel= "stylesheet" type= "Text/css" href= "common.css?time=20060408"/> The value of the parameter time is set to the date of the change on the same day whenever the CSS file is changed. This way, local IE will update it as a new file.
But in the recent project to find a relatively strange problem, the server did gzip compression, to the first time the client decompression is no problem, the second visit when IE read files from the cache is a problem, can only read out the front about one thousand or two thousand bytes. The problem is reproduced on two win2000+ie6 machines, and XP has not yet been discovered.
The final solution is to add a. css ending after the timestamp parameter, which means:
<link rel= "stylesheet" type= "Text/css" href= "Common.css?time=20060408.css"/> Then everything is ok ...
Probably when IE reads a file from the cache, it has to make a judgment on the file name extension, so add it to the recognition. I'm not quite satisfied with this explanation, so if you have a standard answer, please leave a message.
Of course JS can also use this method <script language= "JavaScript" src= "/flash/duilian.js?time=new Date ()" ></script>