Not working in FF24 or Palemoon 24

[GoogleCodeExporter]

What steps will reproduce the problem?
1. blank Palemoon 24 as well as Firefox 24 profile
2. install HTTPS Finder 0.89
3. go to e.g. https://www.kdg.be, confirm SSL connection works
4. go to http://www.kdg.be

What is the expected output? What do you see instead?
It should redirect to HTTPS or display the notification about it. Neither 
happens, tried both settings in both fresh profiles.

What version of the product are you using? On what operating system?
Win7 x32 Home, Firefox 24, Palemoon 24

Original issue reported on code.google.com by therealf...@gmail.com on 23 Sep 2013 at 9:51

[GoogleCodeExporter]

For clarity, before the update from Palemoon 20 to 24, HTTPS Finder would 
redirect me to SSL a few times a day on previously unvisited sites/bookmarked 
sites. Ever since the update to v24 (2 weeks ago), I haven't seen it do 
anything and any attempts to deliberately trigger it (kdg.be, youtube.com, 
wikipedia.org) fail. Official Firefox has the same problem.

Original comment by therealf...@gmail.com on 24 Sep 2013 at 9:29

[GoogleCodeExporter]

Seeing this too. The version 24 incompatibility was discovered in the issue 
#75. Link below:

https://code.google.com/p/https-finder/issues/detail?id=75

I really hope we'll have a solution soon. This addon is wonderful and I 
appreciate all the work the developer has put into it.

Original comment by finnishf...@gmail.com on 26 Sep 2013 at 8:45

[GoogleCodeExporter]

I was using this and HTTPS-Everywhere together for a while. I thought it was 
working, but now I realize it doesn't do anything. None of the prompts ever 
appear, the pages don't switch to HTTPS when auto-enforce is enabled. No rules 
for HTTPS-Eveerywhere.

Original comment by dqe...@gmail.com on 31 Oct 2013 at 5:31

[GoogleCodeExporter]

I don't mean to push, but is there any prospect of an update landing soon? :/ I 
miss HTTPSF and HTTPSE a lot

Original comment by therealf...@gmail.com on 19 Nov 2013 at 1:47

[GoogleCodeExporter]

The problem seems to be that nsIX509Cert.verifyForUsage was removed, making 
line 339 in HTTPSDetect.ks invalid... Mozilla posted the replacement for it 
here: 
https://developer.mozilla.org/en-US/docs/How_to_check_the_security_state_of_an_X
MLHTTPRequest_over_SSL

Hoping that's of any help... I might as well give it a try to patch it myself, 
though I have little experience with advanced stuff like this in JS

Original comment by therealf...@gmail.com on 19 Nov 2013 at 2:05

[GoogleCodeExporter]

Ok, the code in HTTPSDetect goes way over my head... Would anyone else be 
capable of replacing the VerifyForUsage line with the code provided by Mozilla 
(in my previous post)? That's all that needs to be done to make HTTPS Finder 
work again.

Original comment by therealf...@gmail.com on 19 Nov 2013 at 4:16

[GoogleCodeExporter]

Thanks for the prodding on this.. It's been so long since I wrote the addon, 
and it seems like every new FX version breaks something. I'm not adding any 
functionality but ideally would like to make the addon still available for 
those who want to use it..

I'll work on updating the cert verification method and hopefully have something 
in the next week or so.

Original comment by jacobsK...@gmail.com on 19 Nov 2013 at 5:42

[GoogleCodeExporter]

Original comment by jacobsK...@gmail.com on 19 Nov 2013 at 5:43

• Changed state: Started

[GoogleCodeExporter]

Yeah, breaking stuff people need, removing useful things that are not excessive 
and adding stuff nobody wants is Mozilla's mission lately...

Original comment by therealf...@gmail.com on 19 Nov 2013 at 5:59

[GoogleCodeExporter]

Perhaps rewriting HTTPS Finder using the SDK would simplify the code and 
prevent future breakages? Or does it require functionality the SDK doesn't 
offer?

Original comment by therealf...@gmail.com on 20 Nov 2013 at 4:02

[GoogleCodeExporter]

That would take a lot more time than I have to spend on it unfortunately, and 
I'm not sure how much it would improve things. 

Mozilla could help the situation by making their addon compatibility checker 
recognize the use of removed APIs. Instead, I get a "Congratulations, your 
addon will work with Firefox xx.x!" email, followed by user reports of breakage 
a few weeks later. This is why I removed it from the addon store.

Original comment by jacobsK...@gmail.com on 20 Nov 2013 at 4:26

[GoogleCodeExporter]

New version is here: 
https://code.google.com/p/https-finder/downloads/detail?name=httpsfinder_0.90.xp
i utilizing the new cert verification methods. Please let me know if you have 
any issues with this build. 

Thanks!

Original comment by jacobsK...@gmail.com on 30 Nov 2013 at 7:00

• Changed state: Fixed

[GoogleCodeExporter]

Works wonderfully, many thanks :)

Original comment by therealf...@gmail.com on 30 Nov 2013 at 7:13

[GoogleCodeExporter]

Added 0.91 fixing non-English locale encoding corruption issue. It's 
functionally the same as 0.90. Closing this bug!

Original comment by jacobsK...@gmail.com on 1 Dec 2013 at 5:04

• Changed state: Verified