搜尋 Mozilla 技術支援網站

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

了解更多

Google search uses https but appears to return undecryped results

  • 2 回覆
  • 6 有這個問題
  • 1 次檢視
  • 最近回覆由 i_m_f

more options

Since upgrading to v14, I find that whenever I type in a google search in the search bar or in the Firefox start page, the results come back as a page of unreadable characters (e.g. a question mark on a black triangle background). I have noticed that the search is using an https address. If I remove the s from the https part of the URL being generated by Firefox from the address bar and hit Enter, it comes back as normal. It looks as though the search is retrieving encrypted results but Firefox is not decrypting the results or not decrypting them properly and just display the encrypted results.

Since upgrading to v14, I find that whenever I type in a google search in the search bar or in the Firefox start page, the results come back as a page of unreadable characters (e.g. a question mark on a black triangle background). I have noticed that the search is using an https address. If I remove the s from the https part of the URL being generated by Firefox from the address bar and hit Enter, it comes back as normal. It looks as though the search is retrieving encrypted results but Firefox is not decrypting the results or not decrypting them properly and just display the encrypted results.

被選擇的解決方法

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:

從原來的回覆中察看解決方案 👍 3

所有回覆 (2)

more options

選擇的解決方法

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:

more options

Brilliant! Many thanks. This has solved the problem. I had to remove an entry from my user.js file to get this to take effect, as changing the setting in about:config only worked for the current session and then it reverted to the old setting on the next startup. I would never have figured this out without your help. Michael.