[w3c/ServiceWorker] Clarify what needs to be stored from Requests in the cache (#1608)

During #1604 we discussed the Cache API and that Chrome essentially stores enough information about the request for the match algorithm, i.e., URL and headers.

There was some tentative agreement that this might be a good model to standardize upon as matching is the purpose of the cache. If at some point we wanted to take another field into account for matching, this would be possible of course, but it would have to be explicitly added. By default all these fields would end up lost if you put a request into the cache and then get it back out again.

This would mean that these requests cannot be replayed (in detail), but that seems acceptable.

-- 
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/1608