Updates:
Owner: ---
Comment #6 on issue 19298 by [email protected]: Chrome should give up
the first time after getting a 407 DENIED from a proxy server, when
attempting to reach cr-tools.clients.google.com.
http://code.google.com/p/chromium/issues/detail?id=19298
This seems unlikely to be extensions auto-update because (a) extensions are
only
available on dev channel release, (b) they're still turned off by default
unless you
run with a special command-line flag, and (c) we don't have the hosting
gallery public
yet so no one outside of Google should have any installed with an
auto-update url. The
blacklist check code did just go in, but hasn't made it into a dev channel
build yet,
and the url it uses to check is not cr-tools.clients.google.com.
Perhaps this is a bug in Omaha trying to update chrome itself?
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
