A brief analysis of ASP.net page caching

A few days ago encountered a problem, baffled. Later looked at some of the information in mind only a little thought. Make a note of your problems and hope to give some help to other friends of the park.

Here's the thing. One of my asp.net pages has not been updated with window.open navigation and no access to the server when I visit it again. But this phenomenon did not appear on my machine, and other machines in the project team have this problem. At that time I this depressed na, because inconvenient debugging, finally on the page output a lot of alert. Finally found the problem after several experiments.

The main problem is IE cache the page, when the server side of the update, IE did not check. My machine is no problem because my IE is set to check for updates every time I visit the page, and they automatically check for updates. Because I navigate to the page again with the front-end window.open method, this method does not make the browser's automatic check work.

The above narrative is rather messy, I do not know if we can understand. Below I say the concrete solution.

Method One: Use the server-side Response.Redirect method when navigating, or use the front-end Window.location.replace method.

Method Two: Disable ASP.net page caching.

I still recommend method two when necessary. Because we do not have the development of control browser settings. If the user set IE to never check the update cache problem is not easy to avoid, so still use method two, let IE temporary folder does not exist paging file.

Also, do you want to disable page caching? As a matter of fact, at first I thought the page cache was just cached on the server, and then read a blog

The significance of the discovery cache is still significant. In many cases, the pressure on the server can be greatly reduced. Only in the development process to a lot from the requirements, can not blindly set what attributes.