On 12/5/18 5:03 AM, Christof Gerber wrote:
> I found out through
> https://www.spinics.net/lists/squid/msg84767.html that this is because
> Squid 3.5 is not capable of doing ssl_bump + proxy chaining
> 1. Is this finding still up-to-date , saying that Squid 3.5 does not
> support ssl_bump + proxy
On 5/12/18 8:10 pm, Andreas Moehrlein wrote:
> I use squid as a proxy to enable some http and https sites and redirect all
> other traffic to a captive portal.
> Everything works fine, except for a redirect/deny_info for the not allowed
> https traffic.
>
> Is there a mechanism, I can use to
On 6/12/18 1:03 am, Christof Gerber wrote:
> I have a squid 3.5 as forward proxy that does ssl_bump by default.
> Some traffic I need to forward in addition to a second proxy by proxy
> chaining. The following configuration works for HTTP traffic but not
> with HTTPS. I found out through
>
I have a squid 3.5 as forward proxy that does ssl_bump by default.
Some traffic I need to forward in addition to a second proxy by proxy
chaining. The following configuration works for HTTP traffic but not
with HTTPS. I found out through
https://www.spinics.net/lists/squid/msg84767.html that this
> Hi,
>
> Works “well” on my squid v 4.4 (patched) “ debian 9.
>
> Although the site does not load well, squid does not die:
>
> (…)
>
> TCP_MISS/502 1609 GET
> https://cache.drcleaner.com/extend/home/js/jquery-2.0.0.min.js -
> ORIGINAL_DST/99.84.27.102 text/html
>
> TCP_MISS/403 684 GET
>
