Auto-redetect of auto-blacklisted sites after a specified period

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Visit a website
2. The website does not have a https domain
3. The website is auto-blacklisted
4. The website creates an https site (unknown to user)
5. Because of the previous blacklist, the new https site is never detected 
without user intervention

What is the expected output? What do you see instead?
Feature request: After x days, the auto-blacklisted site will be automatically 
removed from the blacklist to be re-detected again. This would enhance the 
possible security increase from this extension, and prevent errors from sites 
that are tricky to detect (I've seen google.com auto-blacklisted when there is 
a https site, but this is another issue I will look into)

This would require new columns where the sites are stored of
1. the date the site was blacklisted
2. if it was set manually or automatically
It would also require a function to trim the list down if any auto-blacklisted 
sites > x days are detected

What version of the product are you using? On what operating system?
1.0.13 on Chrome 6.0.472.63 

Original issue reported on code.google.com by [email protected] on 28 Sep 2010 at 3:42

[GoogleCodeExporter]

Sounds like a good idea. Do you have any suggestions to how long it should wait 
until it redetects?

With regards to Google ending up on the blacklist, i believe that could be the 
same issue as issue 17. Feel free to revive that bug if you think it's 
necessary.

Original comment by [email protected] on 28 Sep 2010 at 3:57

• Changed state: Accepted
• Added labels: Type-Enhancement, Priority-Low
• Removed labels: Type-Defect, Priority-Medium

[GoogleCodeExporter]

I would suggest that it is a user-defined field, with a default of 60 days.

Also, we should probably think about if a selection of 0 days should be 
possible:
If it is, it would effectively disable the blacklist and severely slow down web 
browsing, but perhaps there is a reason it would be needed.

Original comment by [email protected] on 28 Sep 2010 at 4:16

[GoogleCodeExporter]

Slightly off-topic, but I don't think www.google.com has an SSL domain, they 
have a custom one at https://encrypted.google.com which obviously won't be 
caught by this extension until Issue 8 is done.

Original comment by [email protected] on 30 Sep 2010 at 11:51

[GoogleCodeExporter]

@cgugino:
Disabling the cache of the blacklist might make sense for testing purposes, but 
for actual browsing it would be bad. I don't think that should be possible 
through the options page. However we could let 0 mean keeping the cache forever.

I think that 60 days might be a bit low. Sites usually either have SSL 
certificates or not. It doesn't change much. It doesn't matter much for the 
power user, since it would be customizable, but we need to have a sensible 
default value. I'm just not entirely sure of how much of a nuisance/benefit 
it'll be at different settings.

@shrodes:
They do on https://www.google.com/ but the searches are redirected to 
https://encrypted.google.com/
But as i said in comment 1, this discussion should be on issue 17.

Original comment by [email protected] on 30 Sep 2010 at 3:27

[GoogleCodeExporter]

If this option is implemented I suggest there is another option to turn it off. 
I think the 0 (keep in blacklist until I remove it) option is a good default 
option and those who wish to check to see if a new https version of the site 
has come out then they could change the value to 60(days) or whatever.

Original comment by [email protected] on 7 Oct 2010 at 5:22

[GoogleCodeExporter]

Would suggest to implement the feature to just check all links in blacklist 
periodically.
0 for keep in blacklist, and a default value of 60 or 90 to check for change. 
Adding SSL does not happen often. 

Original comment by [email protected] on 25 Oct 2010 at 7:13

[GoogleCodeExporter]

Is the blacklisted list really needed ?
Indeed, this will force the extension to detect each time if there is an HTTPS 
access ?

Original comment by [email protected] on 26 Nov 2010 at 4:33

[GoogleCodeExporter]

It's needed so the extension won't do an SSL request every time there's an HTTP 
request for the detection.

Original comment by [email protected] on 26 Nov 2010 at 5:58