搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Content Encoding Error

  • 5 回覆
  • 0 有這個問題
  • 2 次檢視
  • 最近回覆由 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])

由 cor-el 於 修改

所有回覆 (5)

more options

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

由 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."