為了改善您的使用體驗，本網站正在進行維護，部分功能暫時無法使用。若本站的文件無法解決您的問題，想要向社群發問的話，請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問，我們的社群成員將很快會回覆您的疑問。

Avatar for Username

搜尋 Mozilla 技術支援網站

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

了解更多

此討論串已被封存。 如果您有需要幫助，請新增一個新問題

GoogleSharing doesn't work now that FF 14 is out

SoItBegins
SoItBegins
more options

I have just updated to Firefox version 14. Firefox's new handling of using Google (from the address or search bar) explicitly bypasses the extension GoogleSharing, which is supposed to send all my Google traffic through an anonymizing proxy.

Since the update, searches from the search bar ('Google'), or opening google.com from the address bar will NOT be proxied by GoogleSharing. Is there a way to fix this so that all traffic to Google is run through the plugin again?

I have temporarily downgraded to Firefox 13.0 until this problem is resolved.

I have just updated to Firefox version 14. Firefox's new handling of using Google (from the address or search bar) explicitly bypasses the extension GoogleSharing, which is supposed to send all my Google traffic through an anonymizing proxy. Since the update, searches from the search bar ('Google'), or opening google.com from the address bar will NOT be proxied by GoogleSharing. Is there a way to fix this so that all traffic to Google is run through the plugin again? I have temporarily downgraded to Firefox 13.0 until this problem is resolved.

所有回覆 (1)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 10 Contributor
more options

This probably is related to using SSL for those searches. I haven't seen an official article on this (not to say there isn't one, but I haven't seen one).

While you have Firefox 13 installed, make a copy of your Google search plugin for safekeeping. On Windows 7 (64-bit), it's here. Hopefully this will help you find it on your system:

C:\Program Files (x86)\Mozilla Firefox\searchplugins

I read one thread on another board that replacing the Firefox 14 plugin with the earlier one uses the old http address. However, I haven't tested that theory.