[squid-users] Squid Cache Issues migration from 5.8 to 6.6

[Jonathan Lee]

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/6c32b603/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: favicon.ico
Type: image/vnd.microsoft.icon
Size: 1406 bytes
Desc: not available
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20240704/6c32b603/attachment.ico>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: favicon.ico
Type: image/vnd.microsoft.icon
Size: 1406 bytes
Desc: not available
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20240704/6c32b603/attachment-0001.ico>