Understanding Storage Quota | Workbox

जेफ पॉसनिक लिखते हैं, वर्कबॉक्स पर wrt

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.

पूर्ण पोस्ट पढ़ें

सेवा श्रमिक वेब पारिस्थितिक तंत्र का एक अद्भुत और अभिन्न हिस्सा हैं, लेकिन अभी भी कुछ गॉथस हैं - और यह उनमें से एक है जो आपको समय से पहले नहीं जानता है, जो आपको काट सकता है।

यह देखना बहुत अच्छा है जैसे वर्कबॉक्स इसे संभालने में सक्षम है और आपको सूचित करता है ताकि आप जान सकें कि क्या होता है।

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.