lists.squid-cache.org> >
> http://lists.squid-cache.org/listinfo/squid-users
>
> --
> @mobile
> --
> Sent from iPhone
> -- next part --
> An HTML attachment was scrubbed...
> URL: <
> http://lists.squid-cache.org/pipermail/squid-users/attachments/20220904
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
excpe
I have a container specification at:
https://github.com/elico/squid-container
if it’s helping you and others.
It’s a simple forward proxy with RAM cache only.
If you want to use CentOS stream 8 you can modify the Dockerfile a bit and it
should work in a similar way.
Eliezer
Eliezer Croi
Hey Rahul,
You can create a customized container like described in the official document
at:
https://docs.aws.amazon.com/AmazonECS/latest/userguide/create-container-image.html
It’s pretty simple and is doable.
You shouldn’t run Squid 5.0.4 since it’s very old and there for would not get
suppo
