Why relevant to BlueCoat and not squid? It happens for the users for both systems and google clearly states that it's related to this specific ip activity. (while bing and others works just fine) Eliezer ---- Eliezer Croitoru Linux System Administrator Mobile: +972-5-28704261 Email: eliezer@xxxxxxxxxxxx -----Original Message----- From: squid-users [mailto:squid-users-bounces@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of Yuri Voinov Sent: Monday, April 3, 2017 10:51 PM To: squid-users@xxxxxxxxxxxxxxxxxxxxx Subject: Re: Google Captcha, can something be done to help it with squid? I guess an issue relevant to BlueCoat, not to Squid. AFAIK BlueCoat ignores RFC. Squid - not. 04.04.2017 1:45, Eliezer Croitoru пишет: > Hey List, > > I got couple complains from couple sysadmins about google forcing > their clients to verify that they are indeed humans in some very horrible ways. > But when they are logged in as a user it's "all good" and the search > is working properly. > These networks are using Squid and BlueCoat for 1k users plus and I am > not sure what to do to ease the clients. > I can verify the clients using a username and password using basic and > digest auth but I am not sure what I can do to make google services > understand that I have no bot in my networks. > > Does anyone noticed such an issue? Did anyone found a specific > solution for this? With squid there is no issue. Only when Squid is torified, but this as expected and no issue. > Maybe some header? Don't think so. It still seems as BlueCoat-relevant, not Squid. > > Thanks, > Eliezer > > ---- > Eliezer Croitoru > Linux System Administrator > Mobile: +972-5-28704261 > Email: eliezer@xxxxxxxxxxxx > > > > > _______________________________________________ > squid-users mailing list > squid-users@xxxxxxxxxxxxxxxxxxxxx > http://lists.squid-cache.org/listinfo/squid-users -- Bugs to the Future _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
