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

Firefox displays entire page with odd characters: �4m=n�꤀�^

  • 3 replies
  • 9 have this problem
  • 31 views
  • Last reply by cor-el

more options

Whenever I try to sign into either my Google or Youtube accounts I get a page filled with �4m=n�꤀�^ Internet Explorer has no problems with these pages. I've emptied my cookies and cache, checked my firewall, re-installed Firefox, tried changing the char encoding and made sure both the SSL and TSL were checked. I had no problems until I updated to version 13.01. How do I fix this!?

Whenever I try to sign into either my Google or Youtube accounts I get a page filled with �4m=n�꤀�^ Internet Explorer has no problems with these pages. I've emptied my cookies and cache, checked my firewall, re-installed Firefox, tried changing the char encoding and made sure both the SSL and TSL were checked. I had no problems until I updated to version 13.01. How do I fix this!?

Chosen solution

You can check the network.http.* prefs on the about:config page and reset all bold user set network.http prefs to the default value via the right-click context menu -> Reset.

Check at least:

  • network.http.accept-encoding: gzip,deflate
Read this answer in context 👍 1

All Replies (3)

more options

Chosen Solution

You can check the network.http.* prefs on the about:config page and reset all bold user set network.http prefs to the default value via the right-click context menu -> Reset.

Check at least:

  • network.http.accept-encoding: gzip,deflate
more options

HAZZAH!!! thank you! i reset "network.http.accept-encoding: gzip,deflate" and it worked perfectly, i'm not sure why it messed after the update but it's fixed now.

more options

You're welcome.

Do you have any idea how the value of that pref got changed?

Did you ever looked before on the about:config page to network.http prefs like that?

Do you have extensions that might have changed this pref?

Were any other network.http prefs changed from the default?