Subject: Re: Mixed Content Bug -- SOLUTION!
Date: Wednesday 22nd March 2006 01:20:29 UTC (over 10 years ago)
It looks like I found the culprit. It is line 79 in dojo/src/storage/browser.js which links to a macromedia shockwave site. This line: /storeParts.push(' codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,0,0"');/ will cause a Mixed-Content error in IE if the you are running on a secure server (https). By modifying the line to: /storeParts.push(' codebase="http*s*://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,0,0"'); / ..the problem goes away. Attached is a bare bones html file that will reproduce the problem. Just by including dojo.js (0.2.2 Kitchen Sink version) in this file and placing it on a secure server, you should see the error reproduced in IE. I have attempted to enter this bug into Dojo's bugtracker. The defect number is #550. As this is my first bug report, please let me know if I did anything wrong Thanks! -Sol sam foster wrote: > iframe_history.html should be in the dojo root - right alongside > dojo.js. It has a role to play in the undo / history functionality, > and that's about all I can tell you - but I'm guessing it wouldnt be > too hard to trigger inadvertently if you've been starting with code > from demos etc. I'm fumbling around, but those mixed content errors > mean something somewhere isnt loading correctly, and if its not > showing up as a request in fiddler, it must be an error like the > about:blank one iframe src you mentioned ... If the fire is out for > now, hopefully someone can come up with a better explanation tommorow. > > Sam > > On 3/20/06, Sol Kindle