We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Èròjà atẹ̀lélànà yii ni a ti fi pamọ́ fọ́jọ́ pípẹ́. Jọ̀wọ́ béèrè ìbéèrè titun bí o bá nílò ìrànwọ́.

Content Encoding Error

  • 5 àwọn èsì
  • 0 ní àwọn ìṣòro yìí
  • 2 views
  • Èsì tí ó kẹ́hìn lọ́wọ́ tgavaras

more options

When people come to my website using Firefox, they get the following error page: "Content Encoding Error." This error does not appear using any other browsers (Chrome, Edge, Safari) using a PC or Mac. The website is: https://radiotapes.com/

Please advise what I need to do. Thank you! Tom Gavaras ([email-removed])

When people come to my website using Firefox, they get the following error page: "Content Encoding Error." This error does not appear using any other browsers (Chrome, Edge, Safari) using a PC or Mac. The website is: https://radiotapes.com/ Please advise what I need to do. Thank you! Tom Gavaras ([email-removed])

Ti ṣàtúnṣe nípa cor-el

All Replies (5)

more options

Looks like a problem with Brotli encoding since it works if I remove 'br' from the accept-encoding header.

Ti ṣàtúnṣe nípa cor-el

more options

Thank you for your reply -- I really appreciate it. I am still having a problem figuring out what I need to change. Your image seems to indicate that line 200 may be the issue, but it does not match when I look at the home page in Dreamweaver. I can't find "br" in the header. Tom

more options

By default Firefox sends this accept-content header to the server "gzip, deflate, br". The 'br' at the end of this header indicates that Firefox supports Brotli (br) encoding, but in your case it looks that the server doesn't support this encoding properly and that Firefox fails to process the response. You can see a big difference in the content-length in both screenshots I posted above:

  • Brotli enabled: content-length: 28207
  • Brotli disabled: content-length: 162701

Maybe contact your hosting company to look into this issue and possibly disable support for Brotli.

more options

The hosting company (GoDaddy) is of no help. I'm still unsure how to correct this problem. I can not find any reference to Brotli. This is very frustrating as to why Firefox is the only browser experiencing this issue.

more options

Please explaine "remove 'br' from the accept-encoding header."