Precache per-resource cap should be applied on network bytes used

Precache per-resource cap should be applied on network bytes used

Currently precache fetches are cancelled when response length reaches
the per-resource limit. This is incorrect for gzipped resources.

BUG=625270
Review-Url: https://codereview.chromium.org/2303653002
Cr-Commit-Position: refs/heads/master@{#421101}
(cherry picked from commit dc12c3dfd755611528561c6e48dec23ae59dea5f)

Committed: https://chromium.googlesource.com/chromium/src/+/9db9657f57cad43fd011f96cf855b7f4da37c362

[Raj, 2016-09-28 18:37:53]

Description was changed from

==========
Precache per-resource cap should be applied on network bytes used

Currently precache fetches are cancelled when response length reaches
the per-resource limit. This is incorrect for gzipped resources.

BUG=625270

Review-Url: https://codereview.chromium.org/2303653002
Cr-Commit-Position: refs/heads/master@{#421101}
(cherry picked from commit dc12c3dfd755611528561c6e48dec23ae59dea5f)
==========

to

==========
Precache per-resource cap should be applied on network bytes used

Currently precache fetches are cancelled when response length reaches
the per-resource limit. This is incorrect for gzipped resources.

BUG=625270

Review-Url: https://codereview.chromium.org/2303653002
Cr-Commit-Position: refs/heads/master@{#421101}
(cherry picked from commit dc12c3dfd755611528561c6e48dec23ae59dea5f)

Committed:
https://chromium.googlesource.com/chromium/src/+/9db9657f57cad43fd011f96cf855...
==========

[Raj, 2016-09-28 18:37:54]

Committed patchset #1 (id:1) manually as
9db9657f57cad43fd011f96cf855b7f4da37c362.