Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(162)

Unified Diff: content/browser/cache_storage/README.md

Issue 3002693002: Revert of [CacheStorage] Pad and bin opaque resource sizes. (Closed)
Patch Set: Created 3 years, 4 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | content/browser/cache_storage/cache_storage.h » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: content/browser/cache_storage/README.md
diff --git a/content/browser/cache_storage/README.md b/content/browser/cache_storage/README.md
index ea05b6c9d5ee6c1d48883d5623cbfab8e724f702..7b3758dab2193227091b2605166083839794ac19 100644
--- a/content/browser/cache_storage/README.md
+++ b/content/browser/cache_storage/README.md
@@ -1,5 +1,5 @@
# Architecture (as of July 29th 2016)
-This document describes the browser-process implementation of the [Cache
+This document descibes the browser-process implementation of the [Cache
Storage specification](
https://slightlyoff.github.io/ServiceWorker/spec/service_worker/index.html).
@@ -152,25 +152,3 @@
callback with a function that will run the callback as well as advance the
scheduler. So long as the operation runs its wrapped callback the scheduler
will advance.
-
-## Opaque Resource Size Obfuscation
-Applications can cache cross-origin resources as per
-[Cross-Origin Resources and CORS](https://www.w3.org/TR/service-workers-1/#cross-origin-resources).
-Opaque responses are also cached, but in order to prevent "leaking" the size
-of opaque responses their sizes are obfuscated. Random padding is added to the
-actual size making it difficult for an attacker to ascertain the actual resource
-size via quota APIs.
-
-When Chromium starts, a new random padding key is generated and used
-for all new caches created. This key is used by each cache to calculate padding
-for opaque resources. Each cache's key is persisted to disk in the cache index file
-
-Each cache maintains the total padding for all opaque resources within the
-cache. This padding is added to the actual resource size when reporting sizes
-to the quota manager.
-
-The padding algorithm version is also written to each cache allowing for it
-to be changed at a future date. CacheStorage will use the persisted key and
-padding from the cache's index unless the padding algorithm has been changed,
-one of values is missing, or deemed to be incorrect. In this situation the cache
-is enumerated and the padding recalculated during open.
« no previous file with comments | « no previous file | content/browser/cache_storage/cache_storage.h » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698