Re: [squid-users] how to ignore "only-if-cached" cache header

Since the setup involved just two squids as siblings, I added
cache_peer_access to prevent forward loops.
Thanks Amos.

On Thu, Mar 17, 2011 at 11:36 PM, Amos Jeffries <squid3_at_treenet.co.nz> wrote:
> On 18/03/11 16:24, Rajkumar Seenivasan wrote:
>>
>> Is there any option to ignore the cache-control header
>> "only-if-cached" when sent by a client?
>> Requests with the above gets a 504 Gateway time-out and X-Squid-Error:
>> ERR_ONLY_IF_CACHED_MISS 0.
>>
>>
>> "You have issued a request with a "only-if-cached" cache control
>> directive.
>> The document was not found in the cache, or it required revalidation
>> prohibited by the only-if-cached directive."
>>
>> I know cache-peer directive can take the option "allow-miss" but this
>> setup has two-way peering and worried about forward loops.
>> Appreciate any help.
>
> Then you have just given the reason why its not a good idea to ignore.
>
> All "allow-miss" does is cause the remote peer to ignore "only-if-cached".
> (ie by not sending the flag).
>
> If your topology is open to forwarding loops then you need to set your
> cache_peer_access ACLs to prevent them starting.
>
> Amos
> --
> Please be using
>  Current Stable Squid 2.7.STABLE9 or 3.1.11
>  Beta testers wanted for 3.2.0.5
>
Received on Wed Mar 23 2011 - 01:40:25 MDT