Instead of ignoring ipfs-sw-* assets, we could let the fetch request go through, and cache it, so unstable servers (inbrowser) are less burdened with requests for all the assets.
However, this could add more issues with caching.. but all assets have content-id-hashes, so a sw caching all the assets for it's deployment should be fine. open to thoughts
Instead of ignoring
ipfs-sw-*assets, we could let the fetch request go through, and cache it, so unstable servers (inbrowser) are less burdened with requests for all the assets.However, this could add more issues with caching.. but all assets have content-id-hashes, so a sw caching all the assets for it's deployment should be fine. open to thoughts