On Tue, 25 Mar 2025 22:25:51 -0700, Jonathan Lee wrote:
> You will need to issue certificates on the devices to make it work right.
> It’s an adventure to
> configure.
oh it's working already. thanks again for the replies!
___
squid-users mailing list
On Tue, 25 Mar 2025 15:41:09 +0100, Dieter Bloms wrote:
> Nowadays, data traffic is encrypted and files are not transmitted in plain
> text.
> Have you activated the ssl_bump so that the proxy can also see the data?
fair point. i'll check ssl_bump. thanks!
Hello Goetz
On Tue, Mar 25, Goetz T. Fischer wrote:
> that works fine except for one thing: the cache sizes don't change at all.
> the folder's size as
> well as the ram used by the squid process are like set in stone. no matter
> what i do they don't
> change at all. even after days and week
hi all,
i ran into a slightly odd problem. i'm using the following settings:
cache_dir aufs /mnt/cache/squid 900 16 256
cache_mem 600 MB
maximum_object_size_in_memory 2 MB
maximum_object_size 10 MB
that works fine except for one thing: the cache sizes don't change at all. the
folder's size as
> I see that note in the documentation predates the protocol change to
> include size parameters.
>
> In modern Squid it only applies to the **response** from certificate
> generator/validator helpers back to Squid.
I sorta assumed such a thing, but wasn't sure.
> Your helper should do what th
I see that note in the documentation predates the protocol change to
include size parameters.
In modern Squid it only applies to the **response** from certificate
generator/validator helpers back to Squid.
Your helper should do what the example 'fake' helper does;
* read one '\n' terminated
I'm currently implementing an extended certificate verification script
for usage with "sslcrtvalidator_program", but I've encountered a hiccup
during that.
The documentation at
https://wiki.squid-cache.org/Features/SslServerCertValidator#helper-communication-protocol
is suggesting that the script
