On 15/08/2014 11:22 p.m., Paul Regan wrote:
Urg, thats like standing front of the class for everyone to stare!
If you are not able to take constructive criticisms, sysadmin is
probably not the best ine of work for you :-)
I see you seem to have found the problem. So consider these a free
On 16/08/2014 8:02 a.m., nuhll wrote:
I got nearly all working. Except Battle.net. This problem seems to known, but
i dont know how to fix.
http://stackoverflow.com/questions/24933962/squid-proxy-blocks-battle-net
That post displays a perfectly working proxy transaction. No sign of an
error
You are at least missing https_port and all the sslproxy_* directives
for outgoing HTTPS. Then also you are probably missing the TLS/SSL
certificate security keys, including any DNS entries for IPSEC, DNSSEC,
DANE, HSTS etc.
Ok, so I generated some keys and added the directives.
On restarting
Take a look at:
http://wiki.squid-cache.org/EliezerCroitoru/Drafts/SSLBUMP
Your squid.conf seems to be too incomplete to allow SSL-Bump to work.
Eliezer
On 08/18/2014 02:16 AM, sq...@proxyplayer.co.uk wrote:
Ok, so I generated some keys and added the directives.
On restarting squid it askes
