Re: Work around for - Access denied from a sibling cache ?

Hi,

There is no logic flaw, but you are subject to one constraint in the design
of Squid. Squid never initiates HTTP connections on its own, it only acts
on users' requests. With the current design, incoming HTTP data is
immediately sent and "cut through." Squid does not buffer the data
and send it to the client upon completion.

Nevertheless, there may be a solution, that's why I'm cc:ing this to
squid-dev.

A.R. Cache Op wrote:
> My thought is for a work around / fix,
>
> IF we get a SIBLING_HIT
>
> AND we get a TCP_MISS/400 response
>
> Squid being a smart little sea creature it is doesn't display the
> dreaded "you are not currently allowed to request XYZ From this cache."
> Instead it re-does the request, probably as some type of REFRESH which
> would force it to be reloaded and downloaded from a PARENT or DIRECT.
>
> Would this work around be possible ? Where is my major logic
> flaw ? :-)

-- 
miguel a.l. paraz  <map@iphil.net>                              +63-2-750-2288
iphil communications, makati city, philippines          <http://www.iphil.net>