Addon will be disabled in firefox 41+ because it is unsigned

[genodeftest]

This addon is unsigned. According to https://support.mozilla.org/en-US/kb/add-on-signing-in-firefox?as=u&utm_source=inproduct it will be disabled in a soon-to-be-released version of firefox. This addon will need to get signed by mozilla to continue working.

[stryx]

There haven't been any commits since April 2014. It seems the author quit this project. I've been looking around for alternatives, but I didn't find any replacement yet. There have been requests for including similar functionality into HTTPS-Everywhere ( https://github.com/EFForg/https-everywhere/issues/2718 ). I'm hoping that at some point this might be happening – or that some HTTPS-Finder fork or other replacement becomes available.

[Mikaela]

I wish Firefox and other mainstream webbrowsers just moved into having this functionality by default. Has anything changed with anything since they started about talking about deprecating http?

[ThrawnCA]

@stryx: You could fork it yourself if you like?

@Mikaela: There are overheads of running a tool like this (eg extra traffic to probe the HTTPS domain), which Mozilla is very unlikely to include in the standard browser.

[Mikaela]

There are overheads of running a tool like this (eg extra traffic to probe the HTTPS domain), which Mozilla is very unlikely to include in the standard browser.

If I recall correctly, Mozilla didn't have any issues with starting to do ANY DNS queries...

[yfdyh000]

The users may be taken to another different site while websites for HTTPS behave differently. So I think Mozilla impossible to promote this point, unless to HSTS or other generic announcement protocol.