# Firefox يواجه انتهاكًا لبروتوكول الشبكة على مواقع Discourse

**URL:** <https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308>\
**Category:** Product Support\
**Created:** [16 سبتمبر 2018، 9:23م 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:** 74

<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:** [28 أكتوبر 2018، 3:50م UTC](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308/74 "2018-10-28T15:50:57Z")

</div>

I also managed to repro this issue by setting Firefox to use a SOCKS 4 proxy while the proxy service is off, so it’s impossible to load the page. I get the same corrupted content error. So one more point to:

> [@Falco](#):
>
> Firefox is throwing this error around (Corrupted Content) for any network level error that happens in a fetch inside a service worker

---

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