When you say "shouldn't", are you advocating against the caching that is handled by service-workers in the fetch event handler to support offline mode?On Monday, April 22, 2024 at 5:03:58 PM UTC-4 Daniel Murphy wrote:There shouldn't be a separate pwa handling of caches vs the browser - it's all the same. You can think of an installed PWA HTML experience as just viewing the tab in a different display mode.On Mon, Apr 22, 2024 at 2:00 PM Aaron Shumaker <aaronshu...@gmail.com> wrote:I'm curious about whether compressed responses get cached in their compressed state? If so, does the browser's response cache versus the PWA's cache differ in this regard?--
You received this message because you are subscribed to the Google Groups "pwa-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pwa-dev+u...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/pwa-dev/fca1c42e-3c80-41b2-9cd2-da1c8b99fb55n%40chromium.org.
I'll clarify, that if you choose not to serve a file from the service-worker managed cache, and pass it on to the browser, the browser could still respond with it's own response cache based on usual rules. Most people view these as two different layers of caching in regards to PWAs. My question was more in regards of how these caches handle compressed responses. Thanks.