Correction I can’t access it from the loop back
Sent from my iPhone
> On Apr 5, 2024, at 22:40, Jonathan Lee wrote:
>
> Can you please help I moved from 5.8 to 6.6 I am getting access denied for
> mgr info.
>
> Http manager is built in now right?
> I can access it from the loopback
> Sent fro
Can you please help I moved from 5.8 to 6.6 I am getting access denied for mgr
info.
Http manager is built in now right?
I can access it from the loopback
Sent from my iPhone
___
squid-users mailing list
squid-users@lists.squid-cache.org
https://lists.s
if (empty($settings['sslproxy_compatibility_mode']) ||
($settings['sslproxy_compatibility_mode'] == 'modern')) {
// Modern cipher suites
$sslproxy_cipher =
"EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECD
On 2024-04-04 03:01, David Komanek wrote:
I do not observe this problem accessing sites running only
on port 80 (no 443 at all), but my configuration is simple:
squid 6.6 as FreeBSD binary package
not much about ssl in the config file though, just passing it through,
no ssl juggling
Your us
On 2024-04-05 08:16, Loučanský Lukáš wrote:
Build Info: GIT V6.8 commit 4bee0c8
Could you please somehow elaborate how this seems to be working?
acl SquidSecureConnectFail squid_error ERR_SECURE_CONNECT_FAIL
acl SquidTLSErrorConnect ssl_error SQUID_TLS_ERR_CONNECT
#tunnel all for connection e
FYI
Squid Object Cache: Version 6.8-VCS
Build Info: GIT V6.8 commit 4bee0c8
Could you please somehow elaborate how this seems to be working?
acl SquidSecureConnectFail squid_error ERR_SECURE_CONNECT_FAIL
acl SquidTLSErrorConnect ssl_error SQUID_TLS_ERR_CONNECT
#tunnel all for connection errors