Closed
Bug 569097
Opened 14 years ago
Closed 14 years ago
e10s HTTP: Let HttpChannelParent::GetInterface result with NO_INTERFACE for nsIBadCertListener2
Categories
(Core :: Networking: HTTP, defect)
Core
Networking: HTTP
Tracking
()
RESOLVED
DUPLICATE
of bug 569098
People
(Reporter: jduell.mcbugs, Assigned: mayhemer)
References
Details
Attachments
(1 file)
2.15 KB,
patch
|
Details | Diff | Splinter Review |
This is much like the HTTP auth case: all we need to do is to figure out how to give the HttpChannelParent the appropriate nsIBadCertListener2 to hand out during GetInterface, and things ought to just work (?)
Without this, test-ipc.xul pops up a "secure connection failed" dialog, which allows the client to see the cert info, but doesn't provide any way to make a cert exception and continue the connection.
I tested this by loading https://mail.yahoo.com/, which on 5/29/10 at least had a bad cert.
Not sure if this depends on bug 536301 or not--Honza?
Reporter | ||
Comment 1•14 years ago
|
||
Honza: feel free to morph this into a larger "security UI" bug if that's the right way to proceed.
Assignee | ||
Comment 2•14 years ago
|
||
Hmmm... I don't think it is that easy...
By default (when loading an html page) callbacks doesn't provide any badCertListener. It is not a precondition for the bad cert error page (it lies somewhere else, already discussed in bug 536301 comment 6).
Few components on chrome are pushing nsIBadCertListener2 implementation manually as callbacks to a channel or xmlhttprequest, to suppress the error. Those seem to be: AddonInstall, UpdateParser, Blocklist.
The first one is using directly an http channel, the last two are using XHR.channel and all set (XHR.)channel.notificationCallbacks = new BadCertListener. Access to channel's notificationCallbacks is able only on the chrome (or better say, with the chrome privileges).
So, for me, patch for this bug is to let HttpChennelParent throw NO_INTERFACE (not DROP_DEAD!) when nsIBadCertListener2 is demanded.
The rest needed to correctly display the bad cert error page should be part of bug 536301 and the security UI browser binding (bug 568504).
-> me
Assignee: nobody → honzab.moz
Status: NEW → ASSIGNED
Summary: e10s HTTP: Hook up nsIBadCertListener2 to HttpChannelParent → e10s HTTP: Let HttpChannelParent::GetInterface result with NO_INTERFACE for nsIBadCertListener2
Assignee | ||
Comment 3•14 years ago
|
||
And also UpdateService's Checker is setting xhr.channel.notificationCallbacks = new BadCertListener.
Assignee | ||
Comment 4•14 years ago
|
||
This makes the bad cert dialog appear w/o any drop_deads. It is IMO sufficient for the initial merge with m-c, however, working on making the exception page appear in bug 536301 and dependent.
Attachment #448425 -
Flags: review?(jduell.mcbugs)
Assignee | ||
Comment 5•14 years ago
|
||
Ups... looks like this patch is completely the same as the already reviewed patch for bug 569098. Differs just in the comment.
Reporter | ||
Comment 6•14 years ago
|
||
Great minds think alike.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Updated•14 years ago
|
Attachment #448425 -
Flags: review?(jduell.mcbugs)
You need to log in
before you can comment on or make changes to this bug.
Description
•