Export to GitHub

https-finder - issue #30

Whitelist is temporary disabled if a https-finder notification is being ignored in another tab


Posted on Jun 10, 2011 by Quick Giraffe

What steps will reproduce the problem? 0. create a working whitelist and make sure it is working. (e.g. www.google.com) 1. Go to a site that will trigger a https-finder notification (in my case http://translate.google.com/support/?hl=en) 2. Ignore the notification either by: 2a. not clicking Add to whitelist/Not now/Save rule; 2b. click the cross button on the notification; or 2c. close the said tab directly. 3. Open a new tab and go to http://www.google.com

What is the expected output? What do you see instead? I expect it will stay at http://www.google.com . But it goes to https://encrypted.google.com/ instead.

What version of the product are you using? On what operating system? I am using https-finder v0.69 in Nightly on Win7 64bit SP1.

Please provide any additional information below. It seems that the bug affects entries in the same domain (google.com) only. I have another whitelist entry (grooveshark.com) but it still works while I am ignoring the notification. I can revert the problem by clicking one of the three buttons on the notification, or clearing temporary whitelist in option.

Comment #1

Posted on Jun 10, 2011 by Swift Ox

Interesting, I haven't been able to reproduce this. Does it do it every time, or just once in a while?

Also, you can open HTTPS Finder Preferences, then in the Advanced tab, turn on "Enable debug logging".

Then open the Error console and select "Messages" at the top. If you repeat the steps and watch the log, does it ever say "Removing www.google.com from whitelist"?

You should be seeing "Canceling detection on www.google.com. Host is whitelisted"

Thanks

Comment #2

Posted on Jun 10, 2011 by Swift Ox

By the way, Error console is Tools > Error Console

Comment #3

Posted on Jun 12, 2011 by Quick Giraffe

I can reproduce the problem every time on my machine (I have only 1 machine so I cannot test it elsewhere). I cannot see "Removing www.google.com from whitelist" when doing the testing.

The attached screenshot is the log I get from a new profile with only https-finder installed in Nightly. The 1st line "Canceling detection on www.google.com. Host is whitelisted" is shown when I first go to http://www.google.com. It acts as a control to show that the whitelist was working. The next 6 lines are shown when I open a new tab and go to http://translate.google.com/support/?hl=en The final 6 lines are shown when I ignore the notification in Google Translate tab, then open a new tab and go to http://www.google.com again, but this time I am redirected to the HTTPS version.

Attachments

Comment #4

Posted on Jun 12, 2011 by Quick Giraffe

If it is related, I get the message Could not read chrome manifest file 'C:\Program Files (x86)\Nightly\extensions{972ce4c6-7e08-4474-a285-3208198ce6fd}\chrome.manifest'. when I open the browser, and a warning Warning: XUL box for _moz_generated_content_after element contained an inline #text child, forcing all its children to be wrapped in a block. Source File: chrome://browser/content/browser.xul Line: 0

Comment #5

Posted on Jun 13, 2011 by Swift Ox

Thanks for the information. I misunderstood and didn't realize you meant the Firefox nightly. I tested and couldn't reproduce in FF5.0b2.

I just moved and don't have internet on my PC yet, but I'll get the newest nightly and test again in the next few days.

Sorry for any inconvenience in the mean time

Comment #6

Posted on Jun 17, 2011 by Swift Ox

What exact version of Firefox are you using? The current nightly is 7.0a1, but, 0.69 compatibility is hard-coded with a max version of 6.0a1.

I tested with 6.0a1 and was unable to reproduce. I'm going to try to have a few other people test though...

Also, have you tried uninstalling/reinstalling the extension?

The two other error console entries you listed are not related to HTTPS Finder.

Comment #7

Posted on Jun 17, 2011 by Quick Giraffe

I am using Nightly, Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0a1) Gecko/20110616 Firefox/7.0a1. I overlook that https-finder 0.69 is not supposed to support 7.0a1. I should have reported it at a later time.

Now that I am using HTTPS Finder 0.71d3 and the problem seems to be fixed.

Comment #8

Posted on Jun 17, 2011 by Swift Ox

Glad to hear it's working again. I'll make sure to test this on 7.x+ before the next release to make sure it's still ok.

Status: Invalid

Labels:
Type-Defect Priority-Medium