[squid-users] Squid Cache Issues migration from 5.8 to 6.6
Jonathan Lee
jonathanlee571 at gmail.com
Thu Jul 4 23:17:53 UTC 2024
It does not recognize this directive
2024/07/04 16:16:46| Processing: url_rewrite_children 32 startup=8 idle=4 concurrency=0
2024/07/04 16:16:46| Processing: tls-default-ca on
2024/07/04 16:16:46| /usr/local/etc/squid/squid.conf(235): unrecognized: 'tls-default-ca’
Or with use of =
> On Jul 4, 2024, at 16:12, Jonathan Lee <jonathanlee571 at gmail.com> wrote:
>
> You also stated .. " my current working theory suggests that we are looking at a (default) signUntrusted use case.”
>
> I noticed for Squid documents that default is now set to off ..
>
> http://www.squid-cache.org/Versions/v5/cfgman/http_port.html
>
> http://www.squid-cache.org/Versions/v6/cfgman/http_port.html
> tls-default-ca[=off]
> Whether to use the system Trusted CAs. Default is OFF.
> Would enabling this resolve the problem in Squid 6.6 for error. In theory if default is auto off and it is attempting to use one it would be untrusted automagically after migration
>
>> On Jul 4, 2024, at 14:45, Alex Rousskov <rousskov at measurement-factory.com> wrote:
>>
>> my current working theory suggests that we are looking at a (default) signUntrusted use case.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20240704/96755169/attachment-0001.htm>
More information about the squid-users
mailing list