# Firefox experiences Network Protocol Violation on Discourse based Websites

**URL:** <https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308>\
**Category:** Product Support\
**Created:** [September 16, 2018, 9:23pm UTC](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308 "2018-09-16T21:23:30Z")\
**Posts on this page:** 1\
**Showing post:** 59

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [October 25, 2018, 2:26pm UTC](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308/59 "2018-10-25T14:26:19Z")

</div>

Yeah, that’s true. But since Firefox is throwing this error around (Corrupted Content) for any network level error that happens in a fetch inside a service worker my guess is that it’s a red herring for connectivity problems, aka the page wouldn’t load anyway but with a different error.

And until someone can give proper reproduction steps like I did above, it’s hard to come up with new hypothesis.

---

_[View the full topic](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308)._