-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey James,
I would also appreciate any code that does what you have mentioned.
I can latter write a simple IP\IP_MASK based acl external_acl helper
that can help managing the bump\un-bumped live using some database.
Eliezer
On 12/31/2014 01:11 PM, J
Please James do if it is possible.
Best regards,
Rafael
-Original Message-
From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf
Of James Harper
Sent: Wednesday, December 31, 2014 12:12 PM
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Squid 3 S
And if your ICAP server allows it run it on the same host as Squid to minimize
connection delays from squid <-> icap. E.g. ours (qlproxy) by default is run on
127.0.0.1.
Best regards,
Rafael
From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf
Of Evan Blackstone
Sent:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Also, finally, gents.
Google Drive application uses network:
# Google Drive
74.125.201.0/24
in my region. ;)
So to bypass bump you must specify this network as dst with no bumping.
WBR, Yuri
31.12.2014 18:00, squid-users-requ...@lists.squid-cac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James,
where I can take a look on your helper? I'm interested in this things,
as exists services uses 443 port but without HTTPS. I.e., ICQ, etc.
WBR, Yuri
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQEcBAEBAgAGBQJUo+byAAoJENNXIZxhPexGQ9YH/2
>
> Probably non-HTTPS protocol being used.
>
> As bumping gets more popular we are hearing about a number of services
> abusing port 443 for non-HTTPS protocols on the false assumption that
> the TLS layer goes all the way to the origin server without
> inspection. That has never been a true ass
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 31/12/2014 6:59 p.m., Evan Blackstone wrote:
> Hey all, Wondering if I could get some advice on potentially
> setting up a Squid forward proxy on my network. I'm not a Linux
> novice by any means, but I'm not experienced in server
> administration,
