[w3c/ServiceWorker] consider dropping unnecessary request information when storing in Cache API (#1607)

Currently the Cache API spec is written such that the entire Request is stored as the key in a table.  All information about the Request is preserved.  In theory this allows callers to use `cache.keys()` to get requests back out and initiate a fetch with them.

In practice implementations do not preserve this information in a compatible way.  Gecko has tended to try to preserve all values as indicated by the spec.  Chromium currently only preserves the information necessary for matching; i.e. the url and headers.

Since getting requests back out of `cache.keys()` is a bit niche, do we still want to require storing all information on the request?  For example, things like mode, credentials, destination, internal origin value, etc.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1607