Как в Win 2000 IIS убрать кэширование?

У меня все время выдает старые страницы, а не обновлённые с базы данных.
Мне кажется что все дело в кэш.
Как?

0

Essentials

Here are the the commands to place at the top of your ASP scripts to ensure that the page is not cached:
Response.Expires = 60
is said to expire at 60 seconds, not 0. Also, Khin Zaw (from http://www.asplists.com/asplists/aspadvanced.asp) has posted research from time spent with some IIS internals experts revealing this can be a very touchy parameter to rely upon and usually requires a rather 'large' negative number or pedantically, that would be a very small number).

Response.Expiresabsolute=Now()-2
(my own creation) says 'expire this page 48 hours ago', allowing for time differences, rather than specify a static date. If your page is being viewed by a browser in a very different time-zone it

Response.AddHeader 'pragma','no-cache'
Response.AddHeader 'cache-control','private'
Response.CacheControl = 'no-cache'
their use originates rom an MS KB article. The code is correct but there are some incorrect statements in the article itself.

Some related KB articles include:
http://support.microsoft.com/s... 9.asp?FR=0
http://support.microsoft.com/s... 6.asp?FR=0
http://support.microsoft.com/s... 0.asp?FR=0

If the above techniques do not work in every instance, a 'cache-buster' can be employed.

or
Another thing to remember: Netscape will continue to cache, even if you turn all caching off. This behavior persisted through 4.5 PR1, PR2, and now in the released version of 4.5.

If you fear you might have to deal with caching later, you might want to build contingencies into your app as you go. Retrofitting #5 throughout even a medium-sized app would take a rather sizeable effort. You could retrofit #1-#4 (inclusive) rather quickly with a single pass through the application, but #5 takes a lot of extra effort. And to that end, I don't ever Response.Redirect anywhere in my code except sample code I post to the lists (then again, the only time I use Response.Write is to the list because I rely on my Utilities-Form.inc library for Display() and HTML()). Everything is Redirect(NewURL) where the Redirect function looks like this:
I've learned that I approach things a little differently (sometimes better, sometimes worse, but overall, just differently) and have gotten used to a bunch of tiny little routines scattered throughout my app with a bunch of #include statements. Some of this might seem like overkill, but you have to understand just how pervasive and frustrating caching can

<% Response.Expires = -1 %>

Запрет кеширования на клиенте

<% Response.CacheControl='Private' %>

Запрет кеширования на проксе

0