3 ms·

Looks like FireFox is actually blocking Reddit rather than the other way around. Edit: Firefox blocked the site from loading as it would have been unsafe to at

by krono 5y ago

Looks like FireFox is actually blocking Reddit rather than the other way around. Edit: Firefox blocked the site from loading as it would have been unsafe to attempt due to the encoding problem. I wasn't implying anything else and even posted the browser's own error message. Relax. Check your console: The character encoding of the plain text document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the file needs to be declared in the transfer protocol or file needs to use a byte order mark as an encoding signature.

CyberShadow 5y ago
No, that just means that there is no encoding sent in the header (or HTML http-equiv tag). Anyway, it's back up for me.
- krono 5y ago
  Yes no encoding so unsafe to render, therefore Firefox blocked it. Wasn't implying anything else.
  - CyberShadow 5y ago
    If you saw the word "Blocked", then it did render it.
sdflhasjd 5y ago
It's just a warning firefox is logging because the "Blocked" response is just `text/plain` and doesn't have a header specifying the character encoding.
- krono 5y ago
  Yes, the browser wasn't sure if its render engine would get stuck, but there was a big chance it would only end up dumping a bunch of garbled text on screen anyway (of a different sort than usual :) ). Therefore it decided to simply not load the file at all. In other words, Firefox literally blocked the website from loading and that's precisely what I said.
  - db48x 5y ago
    No, Firefox did not block anything. Firefox contacted the server, and the server sent back a 7–byte text/plain response containing “Blocked”. Since no encoding was specified, Firefox guesses and displays “Blocked” on the screen. Hopefully it was in an encoding you could read, but in case it shows up as mojibake or something Firefox also put a warning in the dev console. The warning isn’t for end users, it is for the developer of the site who is wondering why their site shows up as mojibake.

by krono 5y ago

CyberShadow 5y ago

No, that just means that there is no encoding sent in the header (or HTML http-equiv tag). Anyway, it's back up for me.

krono 5y ago
Yes no encoding so unsafe to render, therefore Firefox blocked it. Wasn't implying anything else.
- CyberShadow 5y ago
  If you saw the word "Blocked", then it did render it.

sdflhasjd 5y ago

It's just a warning firefox is logging because the "Blocked" response is just `text/plain` and doesn't have a header specifying the character encoding.

krono 5y ago
Yes, the browser wasn't sure if its render engine would get stuck, but there was a big chance it would only end up dumping a bunch of garbled text on screen anyway (of a different sort than usual :) ). Therefore it decided to simply not load the file at all. In other words, Firefox literally blocked the website from loading and that's precisely what I said.
- db48x 5y ago
  No, Firefox did not block anything. Firefox contacted the server, and the server sent back a 7–byte text/plain response containing “Blocked”. Since no encoding was specified, Firefox guesses and displays “Blocked” on the screen. Hopefully it was in an encoding you could read, but in case it shows up as mojibake or something Firefox also put a warning in the dev console. The warning isn’t for end users, it is for the developer of the site who is wondering why their site shows up as mojibake.