Understanding Storage Quota | Workbox

Jeff Posnick écrit, à propos de Workbox

A common source of unexpectedly high quota usage is due to runtime caching of opaque responses, which is to say, cross-origin responses to requests made without CORS enabled.

Browsers automatically inflate the quota impact of those opaque responses as a security consideration. In Chrome, for instance, even an opaque response of a few kilobytes will end up contributing around 7 megabytes towards your quota usage.

Lire l'article complet.

Les travailleurs du service font partie intégrante de l’écosystème Web, mais il ya encore beaucoup de pièges - et c’est l’un d’eux qui peut vous mordre si vous ne le savez pas à l’avance.

C'est génial de voir des outils comme Workbox en mesure de gérer cela et de vous informer pour savoir ce qui se passe.

About Me: Paul Kinlan

I lead the Chrome Developer Relations team at Google.

We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.

Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on web.dev, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.