-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/11/2014 11:04 p.m., sq...@icshk.com wrote:
> Hi Amos,
>
> The configuration I post last time still cannot accomplish the
> tasks.
I said the task was not possible.
You are trying to decide whether to authenticate, based on details
that will not
ists.squid-cache.org] On Behalf
Of Amos Jeffries
Sent: Friday, November 07, 2014 4:29 PM
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Squid ACL, SSL-BUMP and authentication questions
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/11/2014 8:35 p.m., squid-list wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/11/2014 8:35 p.m., squid-list wrote:
> Hi, * **"Access to google maps(https://www.google.com/maps) should
> prevent any authentication need"*
>
> I could understand that all users should be able to access the
> google maps link without any authen
Friday, November 07, 2014 3:36 PM
To: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Squid ACL, SSL-BUMP and authentication questions
Hi,
"Access to google maps(https://www.google.com/maps) should prevent any
authentication need"
I could understand that all users should b
Hi,
*
**"Access to google maps(https://www.google.com/maps) should prevent any
authentication need"*
I could understand that all users should be able to access the google
maps link without any authentication. For this you could add the site
acl before the authentication part in the squid conf
Hello all,
As our company policy only allow some machines to access to some SSL website
URL(eg. https://www.google.com/maps). However, they do not have access to
https://www.google.com/ Before, we tried to implement authentication,
everything works fine. We try to allow https access to
https://
