permit google chrome updates

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

permit google chrome updates

Juan Manuel P
I need help to permit google chrome on squid

02/Mar/2021:12:18:01 -0300 || - || 10.114.37.20 || TCP_DENIED/407|| CONNECT || clients1.google.com:443 || text/html


I think that clients1.google.com:443 request are from google chrome.



_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users
Reply | Threaded
Open this post in threaded view
|

Re: permit google chrome updates

Amos Jeffries
Administrator
On 3/03/21 1:21 am, jmpatagonia wrote:
> I need help to permit google chrome on squid
>
> 02/Mar/2021:12:18:01 -0300 || - || 10.114.37.20 || TCP_DENIED/407||
> CONNECT || clients1.google.com:443 || text/html
>


The 407 means authentication is required.

see <https://wiki.squid-cache.org/Features/Authentication>


Amos
_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users
Reply | Threaded
Open this post in threaded view
|

Re: permit google chrome updates

Amos Jeffries
Administrator
On 3/03/21 1:59 am, jmpatagonia wrote:

> Yes the proxy have external authentication --> auth_param basic program
> /usr/lib/squid/basic_ldap_auth....
> but I receive a lot of request from users like
>
> 02/Mar/2021:12:45:02 -0300 || - || xx.xx.xx.xxxx || TCP_DENIED/407||
> CONNECT || update.googleapis.com:443 || text/html
>
> I think the users use the browser for local network services and not
> validate on proxy, but the browser (chrome) still trying to use the
> proxy for update.
>
> How can I fix this ?
>

No secure client will send login credentials unless they are actually
needed. 407 are simply a message from the proxy telling the client to
send credentials, and what type(s) to send (eg Basic).


First check that these requests are not followed almost immediately by a
second request from the client with credentials. If that is happening
there is no problem with the client.

Secondly, check if clients are having trouble logging in with correct
credentials. If they are, figure out why. It may be a problem with the
auth helper or your access controls sequence.


Amos
_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users