New issue
Advanced search Search tips

Issue 709705 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Chrome Canary failed to update with "App Transport Security has blocked a cleartext HTTP"

Project Member Reported by esprehn@chromium.org, Apr 8 2017

Issue description

Google Chrome	59.0.3063.0 (Official Build) canary (64-bit)
Revision	eb509f59b8e9f31569d0dad0d90d8f755291d497-refs/heads/master@{#461928}
OS	Mac OS X 10.12.3 (16D32)

2017-04-07 18:06:53.764 GoogleSoftwareUpdateAgent[55286:3202719] App Transport Security has blocked a cleartext HTTP (http://) resource load since it is insecure. Temporary exceptions can be configured via your app's Info.plist file.
 

Comment 1 by tapted@chromium.org, Apr 11 2017

Cc: mark@chromium.org
Labels: Needs-Feedback
Status: Unconfirmed (was: Untriaged)
[mac triage] Has this recovered?

I think I sometimes get stuff like this when travelling and getting redirected to a captive portal registration page.

Comment 2 by mark@chromium.org, Apr 11 2017

Owner: borisv@chromium.org
That’d be Keystone.

Comment 3 by borisv@chromium.org, Apr 11 2017

Esprehn, which version of the updater do you have? I fixed this long time ago. Check the file /Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Info.plist
If the file is not there, check the same one with tilde:
~/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Info.plist

Comment 4 by borisv@chromium.org, Apr 17 2017

Ping.

Comment 5 by mark@chromium.org, Apr 17 2017

Cc: esprehn@chromium.org
Elliott, the ping’s to you.
This was on a macbook I hadn't used in a few months, so perhaps it was before your fix? It was on my home network, so no captive portal.
Project Member

Comment 7 by sheriffbot@chromium.org, Apr 18 2017

Cc: tapted@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "tapted@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 8 by borisv@chromium.org, Apr 18 2017

Thank you, Elliott. I also want to make sure that the machine is updating now. The issue should slow down, but not block updates. If Chrome is still not updating, can you run the ksdiagnostics from here:
/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/ksdiagnostics

Or prefix with tilde, in case of user Keystone:
~/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/ksdiagnostics
Then send me over the .zip file with the logs that the ksdiagnostics generates.
FYI: the internal bug is b/32175149.
I have CFBundleVersion 1.2.8.55, and the machine appears to be correctly updating Chrome again.

Status: Fixed (was: Unconfirmed)
Thanks, Elliot. Marking as fixed then.

Sign in to add a comment