<% Response.CacheC ontrol = "no-cache" %>

[Jason Huang]

Hi,

Kind of spending too much time on the no-cache issue and found out something
like <% Response.CacheC ontrol = "no-cache" %>.
In my ASP.Net, a C# .aspx file, where do I put the <% Response.CacheC ontrol
= "no-cache" %>?
Is this enough to fix the Caching bug?
Thanks for help.

Jason

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,

I think so, I have never do it that way, I use this line in the code behind:

Response.Cache. SetCacheability (HttpCacheabili ty.NoCache);
cheers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation

"Jason Huang" <Ja************ @hotmail.com> wrote in message
news:O7******** ******@TK2MSFTN GP14.phx.gbl...

Hi,

Kind of spending too much time on the no-cache issue and found out
something like <% Response.CacheC ontrol = "no-cache" %>.
In my ASP.Net, a C# .aspx file, where do I put the <%
Response.CacheC ontrol = "no-cache" %>?
Is this enough to fix the Caching bug?
Thanks for help.

Jason

[Joerg Jooss]

Jason Huang wrote:

Hi,

Kind of spending too much time on the no-cache issue and found out
something like <% Response.CacheC ontrol = "no-cache" %>. In my
ASP.Net, a C# .aspx file, where do I put the <%
Response.CacheC ontrol = "no-cache" %>? Is this enough to fix the
Caching bug? Thanks for help.

Um... caching bug?

Anyway, either set the OutputCache directive on your page(s)

<%@ OutputCache Location="None" %>

or set the Cache property of the HttpResponse in your code-behind class:

Response.Cache. SetCacheability (HttpCacheabili ty.NoCache);

(which is equivalent to the directive shown above)

Cheers,
--
http://www.joergjooss.de
mailto:ne****** **@joergjooss.d e