Thanks for the great explanation. Much appreciated.
On Fri, Aug 30, 2019, at 2:10 PM, Alex Rousskov wrote:
> On 8/30/19 2:41 PM, sq...@buglecreek.com wrote:
>
> > All requests will always start with www.example.com / or
> > origin-www.example.com/
>
> If that is true, why check domain na
On 8/30/19 2:41 PM, sq...@buglecreek.com wrote:
> All requests will always start with www.example.com / or
> origin-www.example.com/
If that is true, why check domain names at all? When you write an ACL
that checks for X, it is reasonable to assume that X may not happen. My
evaluation of you
Thank you for the reply. It appears that I had a IP address typo in one of the
cache_peer lines that allowed the requests with /tst/map1 or map2 to slip bye.
It appears to be working. I think you confirmed what I'm trying to do should
work.
One question about your last statement concerning
On 8/30/19 11:44 AM, cred...@eml.cc wrote:
> We use several squid servers in accelerator mode for load balancing to send
> public requests to backend servers. The squids don't do any caching, they
> just forward requests to the backend.
>
> We have cache_peer directives to send the incoming r
We use several squid servers in accelerator mode for load balancing to send
public requests to backend servers. The squids don't do any caching, they
just forward requests to the backend.
We have cache_peer directives to send the incoming requests to the backend
Apache servers. What I need
