GitLab

For security reasons, resources of extensions from the Chrome Web Store
are verified when used. For that content verifier uses hashes of the
resources, signed by Chrome Web Store. These hashes might or might not
be included in the extension archive. Therefore sometimes they are
fetched from the Chrome Web Store only when needed.

If fetching of the hashes fails, extension is disabled because content
verifier cannot ensure that it is not corrupted. Unfortunately, this may
lead to false-positive disabling of the extension: if fetch of the
hashes failed, for example, because of bad network. To investigate
whether this happens frequently, this CL adds a new histogram:

 * Extensions.ContentVerification.FetchNetError : network error code
when fetch of the content hashes failed.

Bug: None
Change-Id: I03ff9c104a591579d713a5c939853645bea8ec71
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2426583
Commit-Queue: Oleg Davydov <burunduk@chromium.org>
Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#820237}