# Firefox apresenta violação de protocolo de rede em sites baseados no Discourse
**URL:** https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308
**Category:** Support
**Created:** [Setembro 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:** 20
**Page:** 2
### Author:  [@GregoriusTech](https://meta.discourse.org/u/GregoriusTech)
#### Post date: [Setembro 18, 2018, 9:55pm UTC](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308/23 "2018-09-18T21:55:42Z")
While this might be the case, Discourse is the only Site I frequent that causes this Issue. Anything else works just fine, even if there is Network Issues or broken WIFI (Well fine as in Firefox knows the Network is offline as opposed to trying to connect and failing with a Network Protocol Violation).
---
### Author:  [@OvermindDL1](https://meta.discourse.org/u/OvermindDL1)
#### Post date: [Setembro 19, 2018, 12:42am UTC](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308/24 "2018-09-19T00:42:07Z")
> [@jmana9](#):
>
> I believe that the plugin Privacy Badger causes this to happen _a lot_ with all Discourse sites, for me and one other Firefox user who is test-driving Discourse with me. CTRL + F5 fixes the issue temporarily. Whitelisting Discourse sites greatly reduces the occurrence of these errors.
I do not have privacy badger for note.
> [@Falco](#):
>
> 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).
Firefox has also not restarted in weeks.
> [@codinghorror](#):
>
> Are you running any third party Firefox plugins @GregoriusTech? If so run in [safe mode](https://meta.discourse.org/t/53504?silent=true) without them to test. Privacy badger has known issues.
I run uMatrix and some Dark Reader clone, but it still happens in Firefox [safe mode](https://meta.discourse.org/t/53504?silent=true) without extensions.
> [@GregoriusTech](#):
>
> While this might be the case, Discourse is the only Site I frequent that causes this Issue. Anything else works just fine, even if there is Network Issues or broken WIFI (Well fine as in Firefox knows the Network is offline as opposed to trying to connect and failing with a Network Protocol Violation).
Same, I only see it on, and it happens frequently on, any discourse powered site, whether first party or self hosted.
---
### Author:  [@LeoMcA](https://meta.discourse.org/u/LeoMcA)
#### Post date: [Setembro 19, 2018, 2:26pm UTC](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308/25 "2018-09-19T14:26:58Z")
> [@featheredtoast](#):
>
> > 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.
By [triggering a hard refresh](https://developer.mozilla.org/en-US/docs/Web/API/Location/reload) instead of showing the offline page, wouldn’t we get around that problem?
If the server is down, the user will get a proper error; if it’s just their connection being temperamental they’ll either eventually load the site, or get a timeout error.
---
### Author:  [@GregoriusTech](https://meta.discourse.org/u/GregoriusTech)
#### Post date: [Setembro 20, 2018, 5:24pm UTC](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308/26 "2018-09-20T17:24:31Z")
I would be fine if it at least loaded the page properly on the first try. Right now people dont even register to my Forums because the whole oauth popup window is giving that same error and they think everything is broken and highly insecure. And i had that popup breaking on this meta discourse forum too, when I registered to make this report. (see screenshot)
Something should to be done to address the issue, and I would be sad if I heard something along the lines of “lets bug Firefox until they never fix it”, because I am very sure they will just say “Fix your Website”, and then we get the eternal ping-pong of nothing ever happening on either Side. And I did get this vibe from a few (but ofcourse not all) people here, it just happened too often to me when developing stuff, to not notice it when it is likely to happen.
But I’m a tad bit paranoid and dont know people here, so please prove me wrong. 😉
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [Setembro 20, 2018, 8:13pm UTC](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308/27 "2018-09-20T20:13:38Z")
We don’t have any customers (out of 600+ customers) reporting this problem, so it is likely specific to your configuration or networking somehow.
---
### Author:  [@GregoriusTech](https://meta.discourse.org/u/GregoriusTech)
#### Post date: [Setembro 21, 2018, 1:07am UTC](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308/28 "2018-09-21T01:07:37Z")
So I tried it on Firefox on my old Windows 8 Laptop (ofcourse Firefox got updated to Version 62 before the Test) and it did not happen there (Same Router doing the Internet).
To compile all the Info together:
- my zotac zbox + Kubuntu 18.04 + Firefox 62 + no extensions + my network setup = error on first try, always
- my Asus laptop + Windows 8 + Firefox 62 + my network setup = works
- device from someone who complained to me + linux mint + Firefox 62 + no extensions = error on first try, always
- proprietary company computers + windows 10 + Firefox 62 = sometimes error sometimes works
- Firefox + Privacy Badger = sometimes error sometimes works
- Crappy Asus Netbook + Wireless Dongle = sometimes error
- Someone, who told me this happens without specifying any of their system details = error
So I doubt it’s just particular Setups, since it can happen to any OS (unsure if Apple is affected) and with any Network. The only thing they have in common is a somewhat up to date Firefox and that they are somehow logged into Discourse or trying to do so.
And since it doesn’t affect any other sites in Firefox this way (in this consistent fashion), I would bet its somewhere in Discourse, maybe one of the Lines mentioned in previous comments.
---
### Author:  [@jmana9](https://meta.discourse.org/u/jmana9)
#### Post date: [Setembro 21, 2018, 1:22am UTC](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308/29 "2018-09-21T01:22:51Z")
It’s happened to me a few times since I posted 3 days ago. Maybe I jinxed myself. I can also confirm that I’ve only seen this error on Discourse sites, including this one, [freepbx.org](http://freepbx.org), and my own. I’m on Firefox 62.0.
A new version of Privacy Badger was just released today. I just updated. I’ll report back if I encounter any issues.
---
### Author:  [@GregoriusTech](https://meta.discourse.org/u/GregoriusTech)
#### Post date: [Setembro 23, 2018, 7:28pm UTC](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308/30 "2018-09-23T19:28:04Z")
And I got another Report from a Firefox User who has this Issue. Same Firefox Version and same Kubuntu Version that I have though. He gave me this Screenshot.
---
### Author:  [@OvermindDL1](https://meta.discourse.org/u/OvermindDL1)
#### Post date: [Setembro 25, 2018, 1:32am UTC](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308/31 "2018-09-25T01:32:05Z")
> [@codinghorror](#):
>
> We don’t have any customers (out of 600+ customers) reporting this problem, so it is likely specific to your configuration or networking somehow.
I’ve seen people complaining about it on a large number of discourse forums, they are usually ignored as a ‘refresh fixes it’. But it happens on these forums itself, on other forums, for quite a number of people, etc… It is quite a bad user experience. Personally I’ve seen it here at [meta.discourse.org](http://meta.discourse.org), on the rust forums, elixir forums, gradle forums, every single discourse site that I’ve seen and it’s happened on multiple computers that I use, including my home computer here just a few minutes ago (which is odd because it doesn’t happen that often here, it reminded me of this thread). I still do not have privacy badger, adblock, or the sort, just uMatrix (which I’ve disabled as a test to no avail) and a dark reader extension (also tested disabling to no avail in the past).
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [Setembro 25, 2018, 1:39am UTC](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308/32 "2018-09-25T01:39:05Z")
I recommend switching to Chrome, which does not have these problems. Or any other non-Firefox based browser. You may wish to file bugs against the Firefox project.
---
### Author:  [@OvermindDL1](https://meta.discourse.org/u/OvermindDL1)
#### Post date: [Setembro 25, 2018, 2:07am UTC](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308/33 "2018-09-25T02:07:34Z")
> [@codinghorror](#):
>
> I recommend switching to Chrome, which does not have these problems. Or any other non-Firefox based browser. You may wish to file bugs against the Firefox project.
I already primarily do use chrome (I am right now), not everyone does however, nor do users of the forums, and that initial message is often a very quick turn-off for them and they go away to not return (directly reported as such).
This old post here looks somewhat related:
[https://meta.discourse.org/t/cannot-load-app-for-a-meta-topic/78008](https://meta.discourse.org/t/cannot-load-app-for-a-meta-topic/78008)
The post at elixir forums about it (have to be logged in):
[https://elixirforum.com/t/problem-with-elixirforum-content-error/14885](https://elixirforum.com/t/problem-with-elixirforum-content-error/14885)
A pixls forum discussion (of which clearing the cache, which clears the webworker, fixed it, though who knows for how long):
> **[Corrupted Content Error on Pixls.us web site](https://discuss.pixls.us/t/corrupted-content-error-on-pixls-us-web-site/8011)**
>
> When I try to go to https://discuss.pixls.us, my Firefox browser puts up a screen that says: Corrupted Content Error The site at https://discuss.pixls.us/ has experienced a network protocol violation that cannot be repaired. The page you are...
Manjaro forum:
[https://forum.manjaro.org/t/corrupted-content-error-on-firefox/56148](https://forum.manjaro.org/t/corrupted-content-error-on-firefox/56148)
And loaded firefox in [safe mode](https://meta.discourse.org/t/53504?silent=true), navigated to [https://meta.discourse.org/](https://meta.discourse.org/), site loaded, clicked login, clicked github, and the page that popped up in the little window was (after a flicker of it going through github):
Of which clicking `Try again` and it worked.
> [@codinghorror](#):
>
> I recommend switching to Chrome
So yes, I would love to hear of an idea to get everyone switched to a singular browser as it would make development so much easier in my day job, but that also sounds like stagnation waiting to happen… Until then, if you have any ideas for how to convince multiple non-dev, normal people to switch from their preferred browsers, especially when half the time they access the site then it will not load so they won’t come back anyway, I’m all ears.
Before posting this I tried a few more times in firefox, it seems that it loads fine in the main tab but when loading the github login page then on the redirect back from github it is doing that screen rather consistently. A potentially interesting screenshot:
Note how the site request never even appears as the service worker has hijacked it. When refreshing the page to continue then the service worker is performing a `fetch` request, which then continues the pipeline properly.
Whether a firefox bug or not, it’s only affecting discourse sites on any URL even while running firefox in [safe mode](https://meta.discourse.org/t/53504?silent=true)
---
### Author:  [@OvermindDL1](https://meta.discourse.org/u/OvermindDL1)
#### Post date: [Setembro 25, 2018, 2:09am UTC](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308/34 "2018-09-25T02:09:30Z")
Oh, and I’ve heard of a similar issue happening with safari on iPad’s (but not safari on macosx), though never been able to confirm that so I can’t say one way or the other.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [Setembro 25, 2018, 2:13am UTC](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308/35 "2018-09-25T02:13:58Z")
It is a Firefox bug; you will need to report it to them, not us. We have no control over firefox bugs as we do not work on the Firefox project.
---
### Author:  [@GregoriusTech](https://meta.discourse.org/u/GregoriusTech)
#### Post date: [Setembro 25, 2018, 2:29am UTC](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308/36 "2018-09-25T02:29:53Z")
> [@codinghorror](#):
>
> It is a Firefox bug; you will need to report it to them, not us. We have no control over firefox bugs as we do not work on the Firefox project.
Didn’t the people who actively work on the actual Code of Discourse say in this Thread, that its likely an Issue on Discourse Side? Why are you trying to make people believe its not, without even trying to provide evidence?
> [@codinghorror](#):
>
> I recommend switching to Chrome, which does not have these problems. Or any other non-Firefox based browser. You may wish to file bugs against the Firefox project.
You are kidding, right? People can’t just switch Browsers anytime they want, sometimes they have no choice, sometimes all other choices are bad, or cant even be installed.
What if this Bug actually also happens on Chrome, but Chrome decided to be more forgiving on this Error and just auto-refresh the Page whenever it happens? Then the User wouldn’t see the Issue, but the Issue itself still persists.
So please provide actual Information to this topic other than “Don’t use Firefox, tell Firefox its broken”, even though Firefox might have a good reason to display this Error for the Discourse Service Worker.
---
### Author:  [@Mittineague](https://meta.discourse.org/u/Mittineague)
#### Post date: [Setembro 25, 2018, 2:31am UTC](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308/37 "2018-09-25T02:31:12Z")
> [@codinghorror](#):
>
> Firefox bug
It looks like the solution suggested so far is “clear cache”
> **[Corrupted Content Error when opening GMail | Firefox Support Forum | Mozilla...](https://support.mozilla.org/en-US/questions/1232773)**
> **[I get "corrupted content error" for a site that I can access on a different...](https://support.mozilla.org/en-US/questions/1232935)**
---
### Author:  [@GregoriusTech](https://meta.discourse.org/u/GregoriusTech)
#### Post date: [Setembro 25, 2018, 2:32am UTC](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308/38 "2018-09-25T02:32:30Z")
> [@Mittineague](#):
>
> It looks like the solution suggested so far is “clear cache”
> [Client Challenge](https://support.mozilla.org/en-US/questions/1232773)
> [Client Challenge](https://support.mozilla.org/en-US/questions/1232935)
Yep and that one does definitely not work, especially if its the very first time opening the page (in case of registering an account).
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [Setembro 25, 2018, 2:34am UTC](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308/39 "2018-09-25T02:34:44Z")
I use Firefox full time on my desktop and have never seen this issue.
That said I see **ZERO** value in service worker request interception for any of the features we use on desktop including the desktop push notification plugin, and want to see this removed.
I will remove this myself in a week or two.
---
### Author:  [@OvermindDL1](https://meta.discourse.org/u/OvermindDL1)
#### Post date: [Setembro 25, 2018, 2:41am UTC](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308/41 "2018-09-25T02:41:22Z")
> [@Mittineague](#):
>
> It looks like the solution suggested so far is “clear cache”
Yep, as stated prior, clearing the cache does fix it for a time, then it seems that when the webworker gets re-registered then it starts happening in short order, generally when another tab/window gets popped up via the site, like a 3rd party login request here on the meta site for example.
> [@sam](#):
>
> I use Firefox full time on my desktop and have never seen this issue.
Yeah I see it super-rare at home as well, I can only seem to replicate it by logging out, logging in, then choosing either github or google or so, when they redirect back it just kind of dies with that error again. I can’t get it to replicate any other way. At work on windows 10 and Firefox Dev it happens on every initial load of the site in any new tab, extremely common there.
> [@sam](#):
>
> That said I see **ZERO** value in service worker request interception for any of the features we use on desktop including the desktop push notification plugin, and want to see this removed.
>
> I will remove this myself in a week or two.
Ah awesome, thanks! If I can figure out who told me they had the safari-ipad issue then I’ll have them try again as well at that time.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [Setembro 25, 2018, 2:43am UTC](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308/42 "2018-09-25T02:43:05Z")
> [@OvermindDL1](#):
>
> If I can figure out who told me they had the safari-ipad issue then I’ll have them try again as well at that time.
We already explicitly ban service workers on iOS/Safari AFAIK (cc @tgxworld ) so I do not think this is the same issue. (also if we are already giving Safari “special” treatment, we might as well give Firefox the same free pass)
---
### Author:  [@OvermindDL1](https://meta.discourse.org/u/OvermindDL1)
#### Post date: [Setembro 25, 2018, 2:45am UTC](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308/43 "2018-09-25T02:45:14Z")
> [@sam](#):
>
> We already explicitly ban service workers on iOS/Safari AFAIK (cc @tgxworld ) so I do not think this is the same issue.
It was early this year, march or so I think. The firefox issue has been happening for at least a year for me sporadically, though I think it gave me a protocol violation error or something like that for a while in the same circumstances before changing to the current error that it gives now earlier this year. Would you happen to know when the service-worker being blocked on safari was done off-hand?
[Página anterior](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308.md?page=1)
[Próxima página](https://meta.discourse.org/t/firefox-experiences-network-protocol-violation-on-discourse-based-websites/97308.md?page=3)