Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#8133 closed defect (fixed)

HTTPS Everywhere Causes http://siteinspector.comodo.com/online_scan To Not Show Up Properly

Reported by: goodjohnjr Owned by: pde
Priority: Medium Milestone:
Component: HTTPS Everywhere/EFF-HTTPS Everywhere Version:
Severity: Keywords: httpse-ruleset-bug
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Hello,

I would like to report that HTTPS Everywhere (Firefox) 3.1.3 is causing this website to not show up properly (and maybe a few other Comodo websites and/or pages):

http://siteinspector.comodo.com/online_scan

Disabling the Comodo rule in HTTPS Everywhere fixes this problem.

Child Tickets

Attachments (2)

With Error.jpg (38.6 KB) - added by goodjohnjr 8 years ago.
Without Error.jpg (45.4 KB) - added by goodjohnjr 8 years ago.

Download all attachments as: .zip

Change History (9)

Changed 8 years ago by goodjohnjr

Attachment: With Error.jpg added

Changed 8 years ago by goodjohnjr

Attachment: Without Error.jpg added

comment:1 Changed 8 years ago by pde

Keywords: httpse-ruleset-bug added

comment:2 Changed 8 years ago by mikkoharhanen

Resolution: fixed
Status: newclosed

Siteinspector's certificate matches app.webinspector.com, so I'm going to redirect it there. Nevertheless it still has some mixed content.

https://github.com/mikkoharhanen/https-everywhere/commit/4f819c90028fd0e073c30d795d20669807fcf050

comment:3 in reply to:  2 ; Changed 8 years ago by goodjohnjr

Replying to mikkoharhanen:

Siteinspector's certificate matches app.webinspector.com, so I'm going to redirect it there. Nevertheless it still has some mixed content.

https://github.com/mikkoharhanen/https-everywhere/commit/4f819c90028fd0e073c30d795d20669807fcf050

Thank you. :)

So I guess this fix will be available in the next version of HTTPS Everywhere?

comment:4 in reply to:  3 ; Changed 8 years ago by mikkoharhanen

Replying to goodjohnjr:

So I guess this fix will be available in the next version of HTTPS Everywhere?

Hi,

If the maintainers think that my fix is worth applying, it's possible that this will be fixed in the next stable version. You can also keep your eye on the development releases. Maybe it's there sooner.

I'm just one of the users so take my comment with a grain of salt :) Someone else would be better at answering this...

comment:5 in reply to:  4 Changed 8 years ago by goodjohnjr

Replying to mikkoharhanen:

Replying to goodjohnjr:

So I guess this fix will be available in the next version of HTTPS Everywhere?

Hi,

If the maintainers think that my fix is worth applying, it's possible that this will be fixed in the next stable version. You can also keep your eye on the development releases. Maybe it's there sooner.

I'm just one of the users so take my comment with a grain of salt :) Someone else would be better at answering this...

Thank you for responding, giving your guess/opinion, it sounds good to me. :)

I was just wondering/making sure, so that I can know when to test the fix, for a moment there I almost thought that the fix was already in place (like an anti-virus database update or something). :D

comment:6 in reply to:  4 ; Changed 8 years ago by pde

Replying to mikkoharhanen:

If the maintainers think that my fix is worth applying, it's possible that this will be fixed in the next stable version. You can also keep your eye on the development releases. Maybe it's there sooner.

I've merged all your Comodo into git master, and the fix commit into git 3.0. So these changes will be distributed in the 4.0development.6 and 3.1.4, respectively.

comment:7 in reply to:  6 Changed 8 years ago by goodjohnjr

Replying to pde:

Replying to mikkoharhanen:

If the maintainers think that my fix is worth applying, it's possible that this will be fixed in the next stable version. You can also keep your eye on the development releases. Maybe it's there sooner.

I've merged all your Comodo into git master, and the fix commit into git 3.0. So these changes will be distributed in the 4.0development.6 and 3.1.4, respectively.

Okay, thank you very much for explaining that. :)

Note: See TracTickets for help on using tickets.