Re: Cannot cache FTP request (HTTP experts advise needed)

----- Original Message -----
From: "Dr. Michael Weller" <eowmob@exp-math.uni-essen.de>
To: "Henrik Nordstrom" <hno@hem.passagen.se>
Cc: <squid-users@ircache.net>
Sent: Tuesday, October 31, 2000 9:50 PM
Subject: Re: Cannot cache FTP request (HTTP experts advise needed)

> On Mon, 30 Oct 2000, Henrik Nordstrom wrote:
>
> > The heart of thins is http.c:httpCachableReply(), and this is probably a
> > good place to start when looking into why the object does not get
> > cached.
> >
> > Hmm.. reading the code it even has a comment that such replies are not
> > cached when received from cache peers... I think you will find it if you
> > look for it. A possible "fix" is to change the "return 0" to "return 1"
> > some lines below that. This safeguard probably exists to protect from
> > misbehaving caches.
>
> Well, yes, my actual problem is I do not understand httpCachableReply()
> especially because it checks zillions of internal bits, whose meaning is
> unknown to me. I also do not want to change the caching of the other
> files. Where would I put my "return 1" in httpCachableReply()
> to deal only with this (or only a "little" more) case(s).
>
> That cache peer, btw, is not a real cache but a virus scanner. It really
> makes no sense to leave the caching to the peer here.
>

<without reading the source :-]>
I think what Henrik meant was: squid doesn't differentiate between caching
peer proxies and non-caching peer proxies; and the return 0 to return 1
suggestion was to make squid default to caching replies from peers rather
than default to not caching replies from peers. This might fix your issue
and let cache the http response it recieves from the peer proxy.
Rob

--
To unsubscribe, see http://www.squid-cache.org/mailing-lists.html