Search squid archive

Re: cache_peer_access with myportname acl's?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 16 Nov 2010 14:46:50 -0500, Steven Torres <STorres@xxxxxxxxxxxxxx>
wrote:
> Hey Everyone,
> 
> Can someone help my out with this config, it looks correct and I can't
> find any examples of anyone using cache_peer_access with myportname
acl's.
> Basically I have 6 incoming ports that i want to reverse proxy to 6
other
> ip addresses. I also posted a small piece of the cache log where I think
> the problem is.
> 
> 2010/11/16 14:18:27| fwdComplete: http://10.1.212.100/
> 	status 504
> 2010/11/16 14:18:27| fwdReforward: http://10.1.212.100/?
> 2010/11/16 14:18:27| fwdReforward: No forward-servers left
> 2010/11/16 14:18:27| fwdComplete: not re-forwarding status 504
> 

debug_options 44,3 28,3
 aka peer selection and ACL testing is what you want to see.

Your config appears to be the correct for the intended usage of this ACL.

There was a bug with myportname not being available in some access
controls fixed in 3.1.9. I dont think it was cache_peer_access was one of
those, but if you find that the match is being skipped try that release.

Amos


[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux