On 4/12/18 12:18 pm, johnr wrote:
>> What are your squid.conf settings now?
>
> http_port 3128 ssl-bump
You are missing a CA certificate for the bumping process to use for the
certificates it sends the clients.
Also you do not have any ssl_bump lines here. They are required to tell
Squid which o
>What are your squid.conf settings now?
http_port 3128 ssl-bump
tls_outgoing_options NO_TICKET,ALL,No_SSLv3 min-version=1.0
--
Sent from:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Users-f1019091.html
___
squid-users mailing list
squid-
On 4/12/18 5:23 am, pacolo wrote:
> Hello there,
>
> I am coming to you after having solved my first problems with Squid . Thanks
> again!
>
> Anyway, I am facing another issue with Cache Manager.
>
> I had configured Webmin with the non-SMP mode, so I deployed SMP but Webmin
> doesn't detect th
Hi again,
I forgot to mention the software versions.
CentOS Linux release 7.5.1804 (Core)
Squid 3.5.20-12.el7
Webmin 1.900
Regards!
Paco.
--
Sent from:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Users-f1019091.html
___
squid-users ma
Hello there,
I am coming to you after having solved my first problems with Squid . Thanks
again!
Anyway, I am facing another issue with Cache Manager.
I had configured Webmin with the non-SMP mode, so I deployed SMP but Webmin
doesn't detect the cache dirs configured in squid.conf.
In non-SMP m
On 12/2/18 9:56 PM, Amish wrote:
> Current syntax isn't outright bad. Its decent enough.
I disagree (and can back my opinion up with fact-based reasoning), but I
see no reason to argue about that right now.
> May be squid.conf should have versioning processor at top.
IIRC, feature flags are co
Hello Amos,
>If you have a mix of "/cache${process_number}" and "/cache1" in your
>config files you may still be mixing SMP-aware and SMP-disabled access
>to the "/cache1" path.
That's exactly what happened to us, as I mentioned, we are new in the
Squid's world. I have several years of experienc
