Mozilla Destek’te Ara

Destek dolandırıcılığından kaçının. Mozilla sizden asla bir telefon numarasını aramanızı, mesaj göndermenizi veya kişisel bilgilerinizi paylaşmanızı istemez. Şüpheli durumları “Kötüye kullanım bildir” seçeneğini kullanarak bildirebilirsiniz.

Daha Fazlasını Öğren

Facebook loads as random ASCII characters, Chrome does the same thing. Internet Explorer & Edge work fine

  • 2 yanıt
  • 5 kişi bu sorunu yaşıyor
  • 1 gösterim
  • Son yanıtı yazan: MaxTheCat

more options

Recently Facebook began loading a page full of Random ASCII characters in Firefox. I tried Chrome, and it worked fine until this week, when it too started loading Facebook as random ASCII characters. I'm using Windows 10 64bit on a Dell XPS i5 PC. So far, MS Internet Explorer and Edge are working fine.

Recently Facebook began loading a page full of Random ASCII characters in Firefox. I tried Chrome, and it worked fine until this week, when it too started loading Facebook as random ASCII characters. I'm using Windows 10 64bit on a Dell XPS i5 PC. So far, MS Internet Explorer and Edge are working fine.

Seçilen çözüm

Firefox 44+ accepts a new kind of encoding (compression) called Brotli (br) for secure connections. Facebook has recently enabled Brotli (br) encoding for files send via a secure connections. Some security software that intercepts a secure connection to scan the content doesn't know about this encoding and changes the content-type header to text/plain.

A possible workaround is to modify the involved pref and remove the trailing ", br" to prevent the server from sending files with Brotli compression.

  • network.http.accept-encoding.secure = "gzip, deflate, br" => "gzip, deflate" (without quotes)

You can open the about:config page via the location/address bar. You can accept the warning and click "I'll be careful" to continue.

Bu yanıtı konu içinde okuyun 👍 3

Tüm Yanıtlar (2)

more options

Seçilen çözüm

Firefox 44+ accepts a new kind of encoding (compression) called Brotli (br) for secure connections. Facebook has recently enabled Brotli (br) encoding for files send via a secure connections. Some security software that intercepts a secure connection to scan the content doesn't know about this encoding and changes the content-type header to text/plain.

A possible workaround is to modify the involved pref and remove the trailing ", br" to prevent the server from sending files with Brotli compression.

  • network.http.accept-encoding.secure = "gzip, deflate, br" => "gzip, deflate" (without quotes)

You can open the about:config page via the location/address bar. You can accept the warning and click "I'll be careful" to continue.

more options

That did the trick cor-el. I'm assuming the fix for Chrome is similar. Anyways, I've been using Firefox for 10+ years, and it felt very strange using the other browsers. Thanks a bunch for your help, and for restoring my "Happy Place" lol...Peace and out

Steve Piantedosi