javawzl
1/26/2007 6:57:00 PM
We are getting a 200 response on the web page itself; but do get 304s on the
media within the page (after the first load) - images, etc.
Looking at Fiddler, the cacheability is also set to Private ... yet it still
retrieves a new copy each time!
"Joerg Jooss" wrote:
> Thus wrote javawzl,
>
> > We have the following directive in a .Net 2 page -
> >
> > <%@ OutputCache Duration="1800" VaryByParam="None"
> > Location="ServerAndClient" %>
> >
> > However, when watching the request/response through Fiddler, the
> > entire page stream seems to be returned each time ... rather than
> > pulling it from the browser cache.
> >
> > Any ideas what could be causing this? When will it be cached on the
> > Server and when will it be cached on the Client?
>
> It will be
> -- cacheable on the client until the duration has expired and
> -- cached on the server until either the duration has expired, or the page
> has been updated (i.e. ASP.NET detects that it needs to recompile the page).
>
> While the page's cacheability hasn't expired, you'll get a 304 response if
> you hit the server again, or a 200 response of the server-side cached copy
> if it's an end-to-end reload (e.g. using CTRL-F5 in your browser).
> Thus, even in the case of an end-to-end reload, no code is being executed.
>
> How did you test this scenario?
>
> Cheers,
> --
> Joerg Jooss
> news-reply@joergjooss.de
>
>
>