搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

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.