Re: [squid-users] Fwd: cache_peer_access by dynamic ACL

2023-04-20 Thread Alex Rousskov
On 4/20/23 16:18, Amos Jeffries wrote: On 21/04/2023 6:31 am, Alex Rousskov wrote: On 4/20/23 13:14, Alexeyяр Gruzdov wrote: Tell me please If I right understood I could to get answer like "name=value" from my ACL ext script, instead of "OK" or "ERR", right? Not "instead", but in addition to

Re: [squid-users] Fwd: cache_peer_access by dynamic ACL

2023-04-20 Thread Amos Jeffries
On 21/04/2023 6:31 am, Alex Rousskov wrote: On 4/20/23 13:14, Alexeyяр Gruzdov wrote: Tell me please If I right understood I could to get answer like "name=value" from my ACL ext script, instead of "OK" or "ERR", right? Not "instead", but in addition to either OK or ERR. Unfortunately, our d

Re: [squid-users] Fwd: cache_peer_access by dynamic ACL

2023-04-20 Thread Alex Rousskov
On 4/20/23 13:14, Alexeyяр Gruzdov wrote: Tell me please If I right understood I could to get answer like "name=value" from my ACL ext script, instead of "OK" or "ERR", right? Not "instead", but in addition to either OK or ERR. Unfortunately, our documentation of the external ACL helper proto

[squid-users] Fwd: cache_peer_access by dynamic ACL

2023-04-20 Thread Alexeyяр Gruzdov
Ok. The last issues fixed. Thank you ! Tell me please If I right understood I could to get answer like "name=value" from my ACL ext script, instead of "OK" or "ERR", right? And does it means - I could to get answer depends from what users authorises in to proxy. For example: If user "Jon" - th

Re: [squid-users] cache_peer_access by dynamic ACL

2023-04-20 Thread Alex Rousskov
On 4/20/23 10:54, Alexeyяр Gruzdov wrote: The cpu is around 100% even no any requests is going Then the problem is most likely in your script. Foe example, the script actively doing something while there are no Squid requests to work on (instead of blocking while waiting for the next Squi

Re: [squid-users] cache_peer_access by dynamic ACL

2023-04-20 Thread Alexeyяр Gruzdov
The cpu is around 100% even no any requests is going For now I left just one cache_peer in configuration and got the new error: commBind Cannot bind socket FD 28 to [::]: (13) Permission denied чт, 20 апр. 2023 г. в 17:21, Alex Rousskov : > On 4/20/23 04:23, Alexeyяр Gruzdov wrote: > > > ca

Re: [squid-users] cache_peer_access by dynamic ACL

2023-04-20 Thread Alex Rousskov
On 4/20/23 04:23, Alexeyяр Gruzdov wrote: cache_peer peerG1.com parent 40001 0 no-query no-digest name=peerG1 external_acl_type ext_proxy_g1_type %LOGIN %DST /usr/local/bin/g1.py acl proxy_g1_ext_mark_acl  ext_proxy_g1_type acl proxy_g1_ext_marked_acl  annotate_transaction proxy=g1 acl proxy

Re: [squid-users] cache_peer_access by dynamic ACL

2023-04-20 Thread Alexeyяр Gruzdov
Thank you! so ok. I configured like: cache_peer peerG1.com parent 40001 0 no-query no-digest name=peerG1 external_acl_type ext_proxy_g1_type %LOGIN %DST /usr/local/bin/g1.py acl proxy_g1_ext_mark_acl ext_proxy_g1_type acl proxy_g1_ext_marked_acl annotate_transaction proxy=g1 acl proxy_peer