Avatar for Username

חיפוש בתמיכה

יש להימנע מהונאות תמיכה. לעולם לא נבקש ממך להתקשר או לשלוח הודעת טקסט למספר טלפון או לשתף מידע אישי. נא לדווח על כל פעילות חשודה באמצעות באפשרות ״דיווח על שימוש לרעה״.

מידע נוסף

אשכול זה הועבר לארכיון. נא לשאול שאלה חדשה אם יש לך צורך בעזרה.

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.