Hello Amos,
This seems to be a solved issue. With your advices, I have manage to
limit all my user except those who had a login starting by cg_*.
1 - annotation of the "cg_*" 's flow :
_# Comptes generiques_
acl userCgPrefix proxy_auth_regex ^cg_
acl markCgGroup annotate_transaction
On 16/09/22 19:11, PERROT Eric DNUM SDCAST BST SSAIM wrote:
Hello Elizer and David,
Sorry for the delay, I have been monopolized by another subject...
I am not sur to understand how note acl could help me. If the idear of
"note acl" is similar to the one proposed by Amos (creating a group
-28704261
>
> Email: ngtech1...@gmail.com
>
> Web: https://ngtech.co.il/ [2]
>
> My-Tube: https://tube.ngtech.co.il/ [3]
>
> FROM: squid-users ON BEHALF OF
> David Touzeau
> SENT: Tuesday, 6 September 2022 18:45
> TO: squid-users@lists.squid-cache.org
&
On 6/09/22 00:56, PERROT Eric DNUM SDCAST BST SSAIM wrote:
Hello,
We use directives "reply_body_max_size", "request_body_max_size" and
"delay_access" to limit upload, download and passband in our infra.
All of which are "fast" type.
This configuration existes since a while, but we have
ubject: Re: [squid-users] [squid][v5.6] : problem with "slow" or "fast" acl
Hi Eric.
We had the same restrictions with the fast or slow ACLs.
Have you thought about creating a squid helper that calculates your needs?
So maybe you can get around this by using the acl &qu
Hi Eric.
We had the same restrictions with the fast or slow ACLs.
Have you thought about creating a squid helper that calculates your needs?
So maybe you can get around this by using the acl "note" acl note xxx
xxx which turns your helper results (slow) into "fast".
Le 05/09/2022 à 14:56,
Hello,
We use directives "reply_body_max_size", "request_body_max_size" and
"delay_access" to limit upload, download and passband in our infra.
This configuration existes since a while, but we have noticed that with
squid v4.16, our delay pool didn't react as we wanted anymore. We were
