kevinjacobs / https-finder Goto Github PK

Not working HTTPS-Finder 0.87 in FF 22 (menu and item of interfaces working, but not finding and don't create new HTTPS rules).
Please, fix it :)

And, if possible, add russian locale for HTTPS-Finder.
This HTTPS-Finder with russian locale: http://forum.mozilla-russia.org/uploaded/https_finder-0.87-fx-ru-MOD.xpi
This only russian locale: http://forum.mozilla-russia.org/uploaded/https_finder-locale-ru-RU.zip

Hello! Can you please add the support of you extension with Encrypted Web, the fork of HTTPS-Everywhere for Pale Moon? https://addons.palemoon.org/extensions/privacy-and-security/encrypted-web/

Timestamp: 21.04.2013 21:25:29
Error: wouldMatch is not defined
Source: chrome://https-everywhere/content/code/HTTPSRules.js
Line: 659

While opening this site, I'm using Firefox 17.0.5 ESR on Gentoo Linux 64bit with HTTPS-Finder 0.87

HTTPS-Everywhere is useless for me without HTTPS-Finder (I would never add rulesets manually), but HTTPS-Finder is too intrusive to let run all the time:

• too slow on high-latency connections
• breaks too many sites
• still triggers where existing "everywhere" rulesets exists

I would love to be able to keep https-finder disabled by default, but have a shortcut, or a toolbar button, or even a menu item in the tools menu to try to discover https rules for the current page only once.

Would it be possible to tag HTTPS-Finder releases on github please?
This can be helpful to download tarballs from github as well as to check for new releases.

Existing tarball releases are a bit inconvenient for automated checks due to inconsistent archive names/versions.

Also last release 0.87 still refers to itself in Preferences-->About as 0.86 so it would be nice to update version number everywhere (including translations) for future releases.

Thanks.

According to Add-On Compatibility Reporter, HTTPS-Finder doesn't support Firefox Multiprocess (also known as Electrolysis). Mozilla has several resources here to help with implementing multiprocess.

Hello, could you provide a HTTPS Finder version for Firefox Mobile, too? I think, especially for mobile devices https encryption is crucial, therefore it would be great if one could use your addon with phones/tablets.

It seems that with a current Firefox Nightly version like 37.0a1 (2015-01-09) this extension stopped working.

Not working HTTPS-Finder 0.89 in FF 24b10 (menu and item of interfaces working, but not finding and don't create new HTTPS rules).

It is likely that this is accursed, after appearance of the new version FF, HTTPS-Finder again not working. =(

Please, if possible, fix it... =^_^=

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.

What happened？

I've updated the preferred style for HTTPS Everywhere rulesets: https://kittens.eff.org/https-everywhere/rulesets

<ruleset name="RabbitMQ">
        <target host="rabbitmq.com" />
        <target host="www.rabbitmq.com" />

        <rule from="^http:"
                to="https:" />
</ruleset>

Since I get a lot of ruleset submissions generated by HTTPS Finder, I'd appreciate if you could update the default output format. This will reduce the friction when accepting ruleset submissions.

Thanks,
Jacob

Whitelist doesn't work for http://rewardscentral.com.au/

can you help me reconfigure a firewall and access an account ?
susan

1. If the user goes to http://www.example.com and https-finder checks wether we can rewrite it to https://www.example.com .
   Pages often load content from third party pages or subdomains
   like images.example.com or scripts.siteb.com.
   We should check if we can rewrite these as well, and add it to example.coms rule in the first case or create a rule for the thirdparty page in the second case

2. The ssl redirect sometimes causes mixed-content warnings and/or ends up with a non trusted certificate (self-signed, not valid for the domain you try to access,expired).
   Those kind of exceptions end up as exclusions,comments and flags in https-everywheres rulesets. It would be nice to add them automatically as well.

Timestamp: 30.04.2013 07:35:26
Error: AlreadyCalledError: Deferred has already fired

Timestamp: 30.04.2013 07:35:36
Error: HTTPS Finder: testCertificate error: TypeError: secInfo.QueryInterface(...).SSLStatus is null

Source: chrome://httpsfinder/content/HTTPSDetect.js
Line: 399

Timestamp: 30.04.2013 07:35:36
Error: AlreadyCalledError: Deferred has already fired

I'm using Firefox ESR 17.0.5 with HTTPSFinder 0.87 and HTTPS Everywhere 3.2 on Gentoo Linux 64 Bit

If i go to a page where https-everywhere already ships a rule which is disabled because it breaks the page (mixedcontent, not valid certs etc)
i do not want https-finder to automatically redirect to https. Most important there is no reason to add a rule which is already there

Hi,

Thanks for your plugin, it's great. Could you make HTTPS autodiscover just an option in HTTPS Everywhere plugin?
Also it would be great to have same feature in Opera, Chrome and Chromium.

Thanks