Re: [squid-users] Squid - Can't visit (government site and Banking Site) - Please help

2020-04-28 Thread russel0901
Hi again sir, deep is kinda deep to absorb on what you said about TLS, handshake and tcp connection will try to research about this and trace the using tcp packet dump, wireshark or cache.log of squid. -- Sent from: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Users-f1019091.html _

Re: [squid-users] Squid - Can't visit (government site and Banking Site) - Please help

2020-04-28 Thread Amos Jeffries
ONn 29/04/20 2:56 am, russel0901 wrote: > Hi again... > > sorry the browser has a configuration, we already static the browser to our > server 10.20.X.X to port > > > about on the message of error: > > This site can’t be reached (on the browser error) > > www.bancnetonline.com took too l

Re: [squid-users] Squid - Can't visit (government site and Banking Site) - Please help

2020-04-28 Thread russel0901
Hi again... sorry the browser has a configuration, we already static the browser to our server 10.20.X.X to port about on the message of error: This site can’t be reached (on the browser error) www.bancnetonline.com took too long to respond. Try: Checking the connection Checking the pr

Re: [squid-users] explicit proxy and iptables

2020-04-28 Thread Matus UHLAR - fantomas
On 27.04.20 15:27, Vieri wrote: I've been using Squid + TPROXY in transparent sslbump mode for quite a while now, but I'd like to use an explicit proxy with user authentication instead. I have Squid on my first firewall/gateway node, and then I have another gateway (node 2) where all the HTTP re

Re: [squid-users] Squid - Can't visit (government site and Banking Site) - Please help

2020-04-28 Thread Matus UHLAR - fantomas
On 27.04.20 10:17, russel0901 wrote: Hi again... sorry i was not shouting just making the message capitalize. the message on my logs is... TCP_TUNNEL/200 39 CONNECT www.bancnetonline.com:443 - HIER_DIRECT/203.131.77.194 - this means that the proxy was asked to connect to destination server an

Re: [squid-users] failing https requests

2020-04-28 Thread Amos Jeffries
On 28/04/20 2:03 am, Adam Weremczuk wrote: > Thanks Amos for the hint. > > Tcpdump in source reveals the following: > > HTTP/1.1 400 Bad Request ... > > Can I determine which of the above is actually causing failures? > The response says the request is bad. So look at the request message to fi

Re: [squid-users] Using a Baltimore root certificate in transparent ssl proxying

2020-04-28 Thread Antony Stone
On Monday 27 April 2020 at 23:44:41, Lei Wen wrote: > The issue we are having right now is the certificate installed on the > container is a self signed cert, we were trying to migrate this cert to a > real trusted CA cert, or a Baltimore root cert. That will not work for an intercepting ("transp