471379 - No chance to ignore SSL certification errors when proxy in use

Status: VERIFIED DUPLICATE of bug 435558

(Camino Graveyard :: General, defect)

Description

[Yuxuan Wang]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en; rv:1.9.0.6pre) Gecko/2008121820 Camino/2.0b1 (like Firefox/3.0.6pre)
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en; rv:1.9.0.6pre) Gecko/2008121820 Camino/2.0b1 (like Firefox/3.0.6pre)

for some HTTPS sites with SSL certification errors, such as https://hosted.fedoraproject.org, I can only get a blank page with error dialog:

===
hosted.fedoraproject.org:443 uses an invalid security certificate.

The certificate is only valid for <a id="cert_domain_link" title="fedorahosted.org">fedorahosted.org</a>

(Error code: ssl_error_bad_cert_domain)
===

and I have no way to ignore this error and continue. I hope there's a button or something that I can add an exception, just like Firefox.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.



According to the MozillaZine forum post (http://forums.mozillazine.org/viewtopic.php?f=12&t=971445), there's some config hide the error page. But I've tried to set browser.xul.error_pages.enabled to true and false, none works.

Comment 1

[Stuart Morgan]

Nobody has been able to reproduce this except using the browser.xul.error_pages.enabled setting. Please remove any personal information from your prefs.js file, then attach it here so we can try to figure out how you are getting into this state.

Comment 2

[Yuxuan Wang]

Attachment: my prefs.js

Comment 3

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

If you originally had the browser.xul.error_pages.enabled pref set to false, you'll need to at the very least open a new window and use that window, and possibly restart Camino (I can't remember now which) to get the new pref setting to take effect, because that pref is a little "sticky" for some reason.

Comment 4

[Yuxuan Wang]

Do I need to do anything about my prefs.js before restart Camino?
I've already restarted Camino and it doesn't help.

Comment 5

[Stuart Morgan]

You don't by any chance have a user.js that sets browser.xul.error_pages.enabled again every time you relaunch, do you?

Assuming not... does this happen without using a proxy? I can't test the prefs file directly because of the proxy settings.

Comment 6

[Yuxuan Wang]

(In reply to comment #5)
> You don't by any chance have a user.js that sets
> browser.xul.error_pages.enabled again every time you relaunch, do you?
> 
> Assuming not... does this happen without using a proxy? I can't test the prefs
> file directly because of the proxy settings.

Oh yes, it's the proxy! without proxy it's OK now.
The proxy I used is Privoxy, so is this a bug of Privoxy or a bug of Camino?

Comment 7

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Does this also happen with Firefox 3.0.x?

Comment 8

[Yuxuan Wang]

(In reply to comment #7)
> Does this also happen with Firefox 3.0.x?

This also happen in Firefox 3.0.5, but not in Firefox 3.1b2

Comment 9

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

OK, this is a dupe of bug 435558, since your proxy is 'localhost'.

Looks like you can work around it by referencing '127.0.0.1' instead of 'localhost' (see bug 435558 comment 0).

Comment 10

[Chris Lawson (gone)]

Heh, guess that's why I never saw this when I was using Privoxy, since I used IP addys all the time...