Currently every page that's loaded as HTTP is tested for HTTPS. It would be good to cache these results and not send needless server requests for HTTPS, But....

Certain sites use HTTPS only for a login page (and not the rest of the site). If we cache a negative result for HTTPS on the homepage, then redirect to a login page (that isn't explicitly forced to HTTPS) and don't detect again, then we may miss the HTTPS version of the page because the result was already cached.

I will look into this in the future. It could be a good feature to have but we'll need to make sure we don't degrade the detection abilities because of it.

There may be sites that, while available over HTTPS, I do not wish to redirect to HTTPS. (I'm encountering this with a site I'm developing and the constant request to redirect to HTTPS is becoming annoying)

Would it make sense to have an option to ignore certain sites?

Check out version 0.34. It has domain whitelisting :)

https://code.google.com/p/https-finder/downloads/detail?name=httpsfinder034.xpi

It was submitted to Mozilla on Friday and should be reviewed by the end of this week. The source is also available: https://addons.mozilla.org/en-US/firefox/files/browse/115563

Comment deleted

Fix in progress in 0.57. Cert errors or non "OK" https responses result in the host being added to the session whitelist.

Fixed and released in 0.65dev build. Will submit to Mozilla this week after a little more testing.

https://code.google.com/p/https-finder/downloads/detail?name=httpsfinder065dev.xpi