You are correct in that it's most likely an iframe src problem. If you set the source to javascript:false; it should work properly. Not all users of IE may see this error. It's only if the security option "Display mixed content" is set to prompt.
Cheers, -js On 1/29/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Well, I installed Firebug (seems pretty cool) and looked very carefully through everything. All links are absolute references. See for yourself! Go to https://universalprintinginc.com/ and click on "Terms of Service" and you'll see the problem. I don't understand the requirement of the iframe, but I guess it's necessary. There are some known issues related to iframes and IE and the SSL connection, specifically that iframes require a src= element. I tried adding a src element, but then thickbox did not function propely, although the SSL mixed warning did go away. Thanks, Ben > I can't believe I'm writing these words, :) but from my experience, > it is unlikely that this is due to an IE bug. I have seen the same > thing before...where the warning about "some items not being secure" > appears in IE but not Firefox. It may have been to some relaxed (or > misconfigured) Firefox preference or something, but from what I > eventually found in my situation, in my opinion, Firefox should have > been triggering the same warning. > > Anyway, I recommend that you use FireBug 1.0 (http://getfirebug.com/) > in Firefox to find out what's causing the issue. Using Firebug's > "Net" tab, inspect the URLs of every asset that your page is loading. > You can invoke a thickbox and see what assets are called in while the > thickbox appears. Note that if you hold your mouse over the asset's > name you will see the full path of the request used to request the > asset. If any of the assets don't start with "https://"; then that's > your culprit. Then it would just be a matter of determining what code > on your page (HTML or JavaScript) is causing that request to occur > and modifying your code accordingly. > > Good Luck! > -THEO- > > P.S. Firebug rules. :) > > > > On Jan 27, 2007, at 8:20 AM, [EMAIL PROTECTED] wrote: > >> Yeah, that's the bug. There are no actual non-SSL connections to >> anything >> going on. Works just fine in Firefox. >> >>> If you are linking to any resources in the page (image/css/js) with a >>> http:// url you will get this message. Might also happen with ajax >>> calls, >>> but not sure. >>> >>> Blair >>> >>> On 1/27/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >>>> >>>> I have a site on an https://domain.com. When I click on a >>>> thickbox-enabled link in IE, I get an error that says somethings are >>>> secure, some are not. Is there a fix for this? Known issue? >>>> >>>> Thanks, >>>> >>>> Ben >>>> >>>> _______________________________________________ >>>> jQuery mailing list >>>> [email protected] >>>> http://jquery.com/discuss/ >>>> >>> _______________________________________________ >>> jQuery mailing list >>> [email protected] >>> http://jquery.com/discuss/ >>> >> >> >> _______________________________________________ >> jQuery mailing list >> [email protected] >> http://jquery.com/discuss/ > > > _______________________________________________ > jQuery mailing list > [email protected] > http://jquery.com/discuss/ > _______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
_______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
