I can successfully connect as long as I don't use squid for either 1 way or 2 way TLS connections. I've also successfully connect via curl. So, I feel like the site's certs are working well. I could be totally off base here but my interpretation of the the 503 (service unavailable) is that squid is timing out on tls handshake? But what is weird is that when using squid I can successfully connect to google using https. So, that is what makes me wonder if it has something to do with the non-standard https port?
On Mon, Nov 30, 2015 at 10:44 AM, Eliezer Croitoru <eliezer@xxxxxxxxxxxx> wrote:
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
| Bart Spedden | Senior Developer |
| +1.720.210.7041 | bart.spedden@xxxxxxxxxxxxxx |
3 | S H A R E | Adobe Digital Marketing Experts | An Adobe® Business Plus Level Solution Partner |
Consulting | Training | Remote Operations Management |
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
