Thank you Amos for your detailed explanation. That helped. Appreciate it.
On Thu, Nov 20, 2014 at 8:28 PM, Amos Jeffries wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 21/11/2014 3:31 a.m., Swapneel Patnekar wrote:
> > Dear Amos,
> >
> > Thank you for your input.
> >
> > The rea
And if doesn't do the proper HTTP CONNECT, is there any way I can make
squid to use HTTP CONNECT and establish a proxy channel? The reason I ask
is because we use HTTP BasicAuth with the origin server and it needs to be
encrypted end-to-end.
Thanks again,
Hector
On Fri, Nov 21, 2014 at 4:15 PM,
Hi Amos,
For the following cache_peer:
> cache_peer forward-proxy.example.com parent 3128 0 name=C
Would squid do the proper HTTP CONNECT before forwarding the request there ?
Thanks,
Hector
On Thu, Nov 13, 2014 at 10:35 PM, Amos Jeffries
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: S
Thank you Amos,
I've implemented http_port 80 ssl-bump options=NO_SSLv3:NO_SSLv2
Yet still the proxy accepts SSLv3 connections in the sniffing protocol.
Something is still wrong.
Best regards
Sebastian
On 21.11.2014 16:29, Amos Jeffries wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/11/2014 3:57 a.m., Sebastian Fohler wrote:
> I've disabled SSLv3 with this option set in my squid.conf file:
>
> sslproxy_options NO_SSLv3 NO_SSLv2
>
> But despite that fact, the squid proxy accepted the configuration
> without any problems, I
I've disabled SSLv3 with this option set in my squid.conf file:
sslproxy_options NO_SSLv3 NO_SSLv2
But despite that fact, the squid proxy accepted the configuration
without any problems, I still get SSLv3 connections working.
I've sniffed the traffice on that interface on the proxy port and if
And it works great ! Thank you Amos for your patch.
In previous Squid 3.3.x DIGEST was very buggy , crash, 407, banners, but now it seems very stable. Perhaps there are some little bugs like this, but now it's usable.
Thanks for your works
http://bugs.squid-cache.org/show_bug.cgi?id=4066
It
