[squid-users] 2 way SSL on a non standard SSL Port
Eliezer Croitoru
eliezer at ngtech.co.il
Mon Nov 30 17:44:20 UTC 2015
It seems like the issue is not in the basic access control but rather in
the TCP level.
a 503 means some kind of network errors in most cases.
Have you tried contacting the site\ip using netcat or openssl -sa ?
Eliezer
On 30/11/2015 19:40, Bart Spedden wrote:
> Well, interestingly, it seems like the install from the rpm worked.
>
> squid -v
>
> Squid Cache: Version 3.5.11
>
> However, I still see the same error. I also tried the following
> configuration thinking that it would allow ssl on any port and I still the
> same error:
>
> #http_access deny CONNECT !SSL_ports
>
> So, maybe the problem has nothing to do with the non-standard SSL port?
>
> Also, Here's the actual error that I'm seeing:
>
> TAG_NONE/503 0 CONNECT
More information about the squid-users
mailing list