# Issue with the Service Worker

**URL:** <https://forum.dfinity.org/t/issue-with-the-service-worker/14884>\
**Category:** Developers\
**Created:** [August 15, 2022, 1:47pm UTC](https://forum.dfinity.org/t/issue-with-the-service-worker/14884 "2022-08-15T13:47:13Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Seb](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/seb/32/10340_2.png) [@Seb](https://forum.dfinity.org/u/Seb)\
**Post date:** [August 15, 2022, 1:47pm UTC](https://forum.dfinity.org/t/issue-with-the-service-worker/14884/1 "2022-08-15T13:47:13Z")

</div>

Hello,  
Since a few days I’m having issues loading the content of my asset canister with the non-raw url : [https://x3ul6-2aaaa-aaaah-abjda-cai.ic0.app/](https://x3ul6-2aaaa-aaaah-abjda-cai.ic0.app/)

The issue is coming from the service worker that cannot verify the body.  
Here is the exact error I’m getting :

 ![Capture d’écran 2022-08-15 à 15.43.01](https://us1.discourse-cdn.com/flex023/uploads/dfn/original/2X/2/2162b440fe0fe9c1cfe076fd229eca4efcf2ecda.png)

Has anyone experimented the same issue ?

Also, how to check the version of the service worker that is currently loaded on my browser ?

---

<div class="post-metadata">

**Author:** ![rckprtr](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/rckprtr/32/809_2.png) [@rckprtr](https://forum.dfinity.org/u/rckprtr)\
**Post date:** [August 15, 2022, 2:24pm UTC](https://forum.dfinity.org/t/issue-with-the-service-worker/14884/2 "2022-08-15T14:24:22Z")

</div>

We are getting reports of this also over the past couple days.

---

<div class="post-metadata">

**Author:** ![yrgg](https://avatars.discourse-cdn.com/v4/letter/y/9f8e36/32.png) [@yrgg](https://forum.dfinity.org/u/yrgg)\
**Post date:** [August 16, 2022, 8:15pm UTC](https://forum.dfinity.org/t/issue-with-the-service-worker/14884/3 "2022-08-16T20:15:26Z")

</div>

In my experience it happens when the payload exceeds the 2MB message limit size.

---

<div class="post-metadata">

**Author:** ![Daniel-Bloom](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/daniel-bloom/32/2862_2.png) [@Daniel-Bloom](https://forum.dfinity.org/u/Daniel-Bloom)\
**Post date:** [August 16, 2022, 11:22pm UTC](https://forum.dfinity.org/t/issue-with-the-service-worker/14884/4 "2022-08-16T23:22:10Z")

</div>

So, long-story short, during one of our rollouts of updates to the boundary nodes, we experienced some issues and had to fallback to the backup BNs, but the backup BNs have an outdated service worker that does not support streaming.

We have since fixed the issue and rolled the primary boundary nodes forward. Additionally, we are working to update the service worker on the backups to prevent this from occurring again.