Re: Not Caching ASP pages?

Response.Cache.Control looks suspicious - should be Response.CacheControl.
I'd say that it isn't getting set, and therefore the 'private' default is
still getting through. Make a manual request to the web server to make sure.

Odd - I'd think that something like Response.Cache.Control would raise an
error if it didn't exist.

On Mon, May 15, 2000 at 09:37:12PM +0200, Henrik Nordstrom wrote:
> Make sure you haven't uncommented the recommended no_cache settings in
> Squid, or URL's with query strings won't be cached.
>
> Also, if the query string is unique on each request then the URL is
> different.
>
> What is said in store.log?
>
> --
> Henrik Nordstrom
> Squid hacker
>
>
>
> hillel@learn.co.za wrote:
> >
> > Greetings
> >
> > Our web pages have the form:
> > http://www.webpage/default.asp?WCI=Lesson&WCU=88
> > Where we have one main asp page, with many parameters
> > that you can pass to it, eg WCI=Lesson&WCU=88,
> > each resulting in a new page.
> >
> > We've added <%Response.Cache.Control="Public"%>
> > and <%Response.Expires=1440%>
> >
> > However, when I look at the access.log the only default.asp
> > pages I get are:
> >
> > 958388943.908 0 213.219.14.137 TCP_MISS/200 7244
> > GET http://192.168.1.10/default.asp? - DIRECT/192.168.1.10 text/html
> >
> > We're using squid as a http accelerator and the web server is at 192.168.1.10.
> >
> > Any help appreciated

-- 
Mark Nottingham, Senior Developer
Akamai Technologies (San Mateo, CA)