On 28/07/22 19:41, ngtech1ltd wrote:
Hey Amos,
I support what you wrote and I do not know why the service provider wants this
but there are some cases
which there is a need to lower the cache ratio of the clients.
Yes I know. This is a query where we could make things worse by jumping
to
Hey Amos,
I support what you wrote and I do not know why the service provider wants this
but there are some cases
which there is a need to lower the cache ratio of the clients.
Usually fast service is what ISPs want but there are couple use cases that I
have seen which makes sense to somehow
Hey Robert,
The docs at http://www.squid-cache.org/Doc/config/acl/ states:
acl aclname ssl::server_name_regex [-i] \.foo\.com ...
# regex matches server name obtained from various sources [fast]
Which and I do not know exactly what it means but it will not work with a
On 7/27/22 5:19 AM, Amos Jeffries wrote:
Also, the "^.*" in your pattern does nothing useful, it should be
omitted.
On 27.07.22 10:44, Grant Taylor wrote:
Is the bounding to the beginning /implicit/? Or will adobe.com also
match hackadobe.com?
in regexp, it will.
However,
adobe\.com$
and
I would assume that if you want to match something like dstdomain you would use:
(^(.*\.)?)adobe\.com$
Or two regex:
\.adobe\.com$
^adobe\.com$
I like very much: https://rubular.com/
Which allows you to see visually the matches.
Eliezer
Eliezer Croitoru
NgTech, Tech Support
