Yes both were before the cache, but I wasn't calling the correct group in
the ACL, which caused the issue.
Thanks for you help.
Now to figure out why it's slow
On Fri, Nov 30, 2018 at 2:17 PM Alex Rousskov <
rouss...@measurement-factory.com> wrote:
> On 11/30/18 11:51 AM, Wire Cutter wrote:
>
On 11/30/18 11:51 AM, Wire Cutter wrote:
> cache_peer_access peerA1 allow port_8080
>
> cache_peer 192.168.1.2 parent 8800 0 round-robin no-query name=peerA1
> Then this is the error I get when I start the service
>
> Bungled /etc/squid/squid.conf line 3148: cache_peer_access peerA1 allow
>
So thats exactly what I did.
#Rules for Peer group - list 1
cache_peer_access peerA1 allow port_8080
cache_peer_access peerA2 allow port_8080
cache_peer_access peerA3 allow port_8080
cache_peer_access peerA4 allow port_8080
#cache_peer
cache_peer 192.168.1.2 pa
On 11/29/18 7:57 AM, Wire Cutter wrote:
> I’ve created 4 ports for clients to talk to, then created ACL lists for
> those ports. From there I’ve tried (and failed) to create naming groups
> for cacheing peers, then added those to ACLs and it fails. Any ideas?
Use cache_peer_access to allow http_
I have an issue with a Squid config I can’t figure out. I’m trying to have
a many (Hosts) to many (Up stream proxies) in a single config
I’ve created 4 ports for clients to talk to, then created ACL lists for
those ports. From there I’ve tried (and failed) to create naming groups
for cacheing pee
