User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.6) Gecko/20040113 Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.6) Gecko/20040113 Using HTTPS, if using one iframe in a document (refering to more ssl content), no problems. Using two iframes results in an insecure data error, "You have requested an encrypted page that contains some unencrypted information ...". This does not seem to be affected by the content of the iframes. I can use the same code for an iframe, twice in a document (same url for each iframe) and receive the same error message so the problems seems to be with using more than one iframe in a secure document. Is there any way to use multiple iframes and avoid this error (broken lock, also). Reproducible: Always Steps to Reproduce: 1.code two iframes in any ssl document 2.load page 3.read error on loading Actual Results: saw Mozilla error message "You have requested an encrypted page that contains some unencrypted information ...". Expected Results: no error I can delete either iframe and the message goes away (does not reoccur). Also, when viewing the "page info" for the iframed documents, the url has "https" inserted correctly. I have tried adding the "https://www..../" to the links but it seems to make no difference. Iframe tags in SSL document <iframe name="show_links" height="20%" width="100%" frameborder="0" scrolling="auto" src="/iacuc/getdata/number 1.pl?order_by=skey&order=abc&index=display_record"></iframe> <hr size="1" width="90%"> <iframe name="show_links" height="20%" width="100%" frameborder="0" scrolling="auto" src="/iacuc/getdata/number 2.pl?order_by=skey&order=abc&index=display_record"></iframe>
I can provide a temporary link if necessary although I'm sure that you can quickly duplicate the problem using local cod if you've acces to a server with SSL.
Summary: Using two iframes on an encrypted (https) page results in an insecure data error. → Using two iframes on an encrypted (https) page results in an insecure data error.
Assignee: general → kaie
Component: Browser-General → Client Library
Product: Browser → PSM
QA Contact: general → bmartin
Version: Trunk → 2.4
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.