Closed
Bug 333807
Opened 18 years ago
Closed 18 years ago
HTTPS in iframe
Categories
(NSS :: Libraries, defect)
NSS
Libraries
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 335859
People
(Reporter: George.siu, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/418 (KHTML, like Gecko) Safari/417.9.2 Build Identifier: I've discovered that if you have a HTTPS from server A that give firefox a page with an iframe to create another HTTPS connection it throws an Error Code -12219 This is repeable on Firefox 1.5.0.1 on Winxp and Mac OS X Example webpage (I'm using a private IP but any should work) <!doctype html public "-//w3c//dtd html 4.0 transitional//en"> <html> <head> </head> <body text="#000000" bgcolor="#CCDDFF"> <center> <iframe name="updates" align="middle" marginheight="0" marginwidth="0" frameborder="0" border="0" src="https://10.10.10.159/helloworld.htm" width="100%" height="100%" noresize="yes" scrolling="auto"> If your browser supported inline frames, you would be seeing <a href="updates.html" target="new">this page</a> in this space. To view it correctly you need Internet Explorer or a Netscape 6+ Compatible browser (Mozilla, Firebox). </iframe> </center> </body> </html> Reproducible: Always Expected Results: The page should display the page with the iframe that was sourced from the https source
Assignee: nobody → nobody
Component: Security → Libraries
Product: Firefox → NSS
QA Contact: firefox → libraries
Comment 1•18 years ago
|
||
Is there any reason to believe that iframes are essential to this report? Does the problem occur if you simply visit the indicated URL in the address bar? (I'll bet that it does.) Kai, SSL_ERROR_CLIENT_KEY_EXCHANGE_FAILURE is another candidate for the TLS intolerant retry list.
Blocks: 107491
Comment 2•18 years ago
|
||
Nelson, I added SSL_ERROR_CLIENT_KEY_EXCHANGE_FAILURE to the patch in bug 335859.
Comment 3•18 years ago
|
||
George, you could try whether your issue is fixed by downloading a mozilla trunk build with a date of tomorrow or later. Please let us know if it fixed your issue.
Depends on: 335859
Comment 4•18 years ago
|
||
In the absence of any reply for 60 days, I am presuming that the fix for bug 335859 also fixed this bug, and am marking this bug a duplicate. *** This bug has been marked as a duplicate of 335859 ***
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•