Opened 7 years ago

Closed 6 years ago

#3360 closed defect (fixed)

HTTPS Everywhere breaks translator addons for firefox

Reported by: Dapper Owned by: pde
Priority: Medium Milestone:
Component: HTTPS Everywhere/EFF-HTTPS Everywhere Version:
Severity: Keywords: Translator addon
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Unforyunatelym with HTTPS Everywhere installed various translator addons fail to work. I have tried a variety of these addons:

Quick Translator
My Translator (Google Translate)
BabelFish Instant Translation

And all fail when attempting to translate selected text.

Child Tickets

Change History (5)

comment:1 in reply to:  description Changed 7 years ago by Dapper

Replying to Dapper:

Unfortunately, with HTTPS Everywhere installed various translator addons fail to work. I have tried a variety of these addons:

Quick Translator
My Translator (Google Translate)
BabelFish Instant Translation

And all fail when attempting to translate selected text.

comment:2 Changed 6 years ago by Anna

This is because all of these addons use services by google and yahoo who do not offer an https connection for the relevant urls. It's not difficult to add an exception to the HTTPS Everywhere rule for googleapis which will make these translation addons work again. You just open the https options, uncheck googleapis, get a new copy of the googleapis rule from EFF's git repository, add the exclusion line for the url that the translation addon uses and then save the rule to your the HTTPS Everywhere folder in your browser profile. I've already done an override of a broken rule using this method and it works fine but I'm not sure it's necessarily a secure option in this case because I don't know what other uses there may be of similar urls to the translation tool (ajax.googleapis.com) and what information the addon collects and sends about what you're reading.

comment:3 Changed 6 years ago by Dapper

Thank you for the feedback, I shall take a look at the options you've suggested :)

comment:4 Changed 6 years ago by pde

Status: newaccepted

Anna, Dapper,

Can either of you tell me if this bug is fixed by default in the 1.0.0development releases of HTTPS Everywhere?

https://www.eff.org/files/https-everywhere-1.0.0development.3.xpi

comment:5 Changed 6 years ago by pde

Resolution: fixed
Status: acceptedclosed

I think this is fixed for real in 1.0.0development.4. Please reopen if it isn't.

Note: See TracTickets for help on using tickets.