# 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:** 19

<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:** [18 سبتمبر 2018، 5:27م UTC](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308/19 "2018-09-18T17:27:52Z")

</div>

> [@GregoriusTech](#):
>
> Funnily enough this even happens when the Internet is fully disconnected. Instead of “Failed to Reach Website” I get “Network Protocol Violation”, meaning the Cache is involved in this aswell.

This a know issue with Privacy Badger: [Is privacy-badger blocking Discourse from loading correctly? · Issue #1953 · EFForg/privacybadger · GitHub](https://github.com/EFForg/privacybadger/issues/1953)

Firefox also had some problems involving service workers and session restore like [1454400 - Session Restore doesn't activate service worker](https://bugzilla.mozilla.org/show_bug.cgi?id=1454400) which affected both Discourse and [Microsoft Developer portal login](https://github.com/MrAlex94/Waterfox/issues/581#issuecomment-391834656).

Looks like there is a new issue with Firefox online detection.

> [@featheredtoast](#):
>
> Wondering if @Falco can chip in for a good path to offline support at this point.

We need to pass the Lighthouse PWA audit, which requires the offline page, which requires the service worker and proxy.

> [@featheredtoast](#):
>
> > [@LeoMcA](#):
> >
> > Could we check if this error is a network error, and show the offline page in that case too? (Or even wait a little bit, and refresh the page for a user?)
> 
> I think we did that before, and it caused some confusion when a discourse _server_ went down, and instead of a “not online” page, we wanted to differentiate that it was actually not responding down and here’s the error vs you being offline.

Exactly, we had that and people complained.

---

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