Delay pools are broken in squid 4.x for https. Work for http only.
"Known" bug, said to be fixed in squid 5.x only.
You might consider using squid 3.x instead.
--
Sent from:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Users-f1019091.html
___
On Linux you can use iptables to do qos and make sure that a single connection
does not consume all bandwidth.
Marcus
On 30/07/2019 10:22, Service MV wrote:
Just to explain clearly, my goal is that no user of my LAN can download more
than 15 megabits/s, because some downloads consume me 100
Hi All.
I need to use Squid with few ICAP services, to be able to check files for
viruses with few antivirus services.
But if i use the chain, the first service modifies the response and the object
isn't being sent to the second service. Instead, the modified content (blocking
page) is being s
On 7/31/19 6:47 AM, Nikita Seregin wrote:
> if i use the chain, the first service modifies the response and the
> object isn't being sent to the second service. Instead, the modified
> content (blocking page) is being sent to the second service.
If you can modify/configure the first ICAP service
On 31/07/19 3:23 pm, kmiku7 wrote:
>
> Thanks your reply.
> I am running 64bit build of squid on 64bit system. The output of top/ps
> shows that squid is using as much memory as claimed in report.
Okay. That means the negative values are just an artifact of 32-bit
types used in the report display
We have been using several squid servers in accelerator mode for a number of
years mainly for load balancing to send public requests to backend servers.
The requests to the squids typically come via a well known commercial caching
service. The squids don't do any caching, they just forward r
Hi,
Squid conf:
acl CONNECT method CONNECT
acl to_bad_ip dst 55.55.2.3
http_access deny CONNECT to_bad_ip
In the above squid config, if I were to try go to https://55.55.2.3:443 I
would get an ACCESS DENIED but squid would not block the CONNECT (it would
respond to 200) and then block the subsequ
On 7/31/19 10:44 PM, johnr wrote:
> acl CONNECT method CONNECT
> acl to_bad_ip dst 55.55.2.3
> http_access deny CONNECT to_bad_ip
> In the above squid config, if I were to try go to https://55.55.2.3:443 I
> would get an ACCESS DENIED but squid would not block the CONNECT (it would
> respond to 2
