Mark Wilson I am the creator of TopXML. I am available for international and local (Australia) contracts. I am a Solution Architect/Business Analyst. I have worked in IT in several countries (NZ, Australia, South Africa, UK) building and training teams for government and very large non-governmental organizations. I am ex-Microsoft Consulting Services. I wrote the first book on Microsoft XML published in 2000 called XML Programming with VB and ASP. Most recently I have been building tools for the SEO industry. Ask me for a 37 point SEO health-checkup for your website.
First posted :
03/24/2008
Times viewed :
791
The Response.CacheControl Property
Introduction
The Response.CacheControl can be used to control the caching
behavior of the asp page. This feature is only useful when you are having a
proxy server between the client and the server. If you don’t use a proxy then
this property will be ignored. Usually all asp pages are cached in the proxy on
the proxy to make the request faster for the user. However in certain pages you
may not want to allow this. Just suppose of a website which delivers news. If
wont be a good idea to cache this website, because news appear nearly each
hour. To avoid this you can simply set the CacheControl to “Private” and the
proxy will not cache the page. Other values can be seen in the below table.
Example
<%
Response.CacheControl
= "Private"
%>
<p>Please enter your bank account number and password
to login</p>
Number: <input type="text"/><br/>
Password: <input
type="password"/><br/>
<input type="submit">
Output
Values
Name:
Description:
Private
This is the default value and can be used if you do not
want the proxy to cache the page.
Public
This property is used if you want to cache the asp page.
