Discourse ベースの Web サイトで Firefox がネットワークプロトコル違反を経験

[Falco]

@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

Firefox also had some problems involving service workers and session restore like 1454400 - Session Restore doesn't activate service worker which affected both Discourse and Microsoft Developer portal login.

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.