You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our implementation will get simpler indeed without having to deal with duplicate requests, and you're right about the inconsistencies with the cache storage API. Cache API doesn't support requests with bodies either, but we plan to support them.
For uploads, developers will want to use the same URL for all requests in the fetch.
If we decide to not to support these, developers will need to add some (unnecessary) query params to each upload URL, to get past our check. This feels non-ideal, and might be seen as a limitation of our implementation.
This discussion is on the spec level so the implementation is irrelevant.
It's true that the cache API doesn't support requests with bodies, but I'm referring to the match/matchAll algorithm, which is being applied to both with a different set of preconditions.
It is only a limitation in so far no duplicates are allowed in a cache.
The spec defines outlines the matching algorithm here: https://w3c.github.io/ServiceWorker/#request-matches-cached-item
A Background Fetch should have the same set of restrictions (duplicate URLs allowed only with an appropriate
Vary
header).The text was updated successfully, but these errors were encountered: