Re: [squid-users] ICAP response to avoid backend

2024-02-27 Thread Ed Neville
On 2024-02-27 12:38+1300, Amos Jeffries wrote: > On 26/02/24 06:52, Ed wrote: > > > >acl bad_foo req_header ICAPHEADER -i foobar > >cache_peer_access server_1 deny bad_foo > Assuming that an ICAP service is controlling whether the peers are to > be used that is the correct way. > > Howe

Re: [squid-users] ICAP response to avoid backend

2024-02-26 Thread Amos Jeffries
On 26/02/24 06:52, Ed wrote: On 2024-02-24 17:26+, Ed wrote: In varnish land this is doable in the vcl_miss hook, but I don't know how to do that in squid. I think I found a way, but maybe there's a better method - I'd like to the cache_peer_access to apply to all backends, but this does s

Re: [squid-users] ICAP response to avoid backend

2024-02-25 Thread Ed
On 2024-02-24 17:26+, Ed wrote: > In varnish land this is doable in the vcl_miss hook, but I don't know > how to do that in squid. I think I found a way, but maybe there's a better method - I'd like to the cache_peer_access to apply to all backends, but this does seem to do what I was after

[squid-users] ICAP response to avoid backend

2024-02-24 Thread Ed
Hi, Does anyone know a way to tell squid in accelerator mode to not go to the backend peers? There's a couple of requests I'd like to avoid handing off to the backend, but, if the data is already a HIT, then I'd like squid to send that, just sometimes I don't want it to send the request to the