IE 8 Secuirty warning on MarkerImage Click in Https

[GoogleCodeExporter]

Demo link or sample code:
At first there was an issue referencing the images over http, I copied and 
referenced them locally to fix that issue, but now a security warning is 
displayed on a ClusterImage Click. I used HttpWatch and I don't see any calls 
to http, and its only on "ClusterClick". If I zoom in using the mouse wheel for 
instance, there is no issue. I'm lost to as what may be causing the issue with 
IE8. Seems like a script issue, but that is just speculation.

What steps will reproduce the problem?
1.Visit a ClusterMap over Https
2.Click on cluster icon
3.Security warning prompt is displayed

Expected result:
Map zooms in on cluster location on cluster icon click.

Actual result:
IE Security warning "Do you want to view only the webpage content that was 
delivered securely?" The map still works fine regardless of selecting "Yes" or 
"No" on the warning prompt.

Version: 3

Browser / Operating System:
IE8 Windows XP

Additional comments:

*********************************************************
Tip: Star this issue (next to title) to receive notifications of status
changes against this issue, also used as a gauge for how many people are
interested in seeing it resolved.
*********************************************************

Original issue reported on code.google.com by victoryi...@gmail.com on 16 Jun 2011 at 3:14

Attachments:

• clusterClickError.png

[GoogleCodeExporter]

Did some more digging, its an issue somewhere within the: 
"this.map_.fitBounds(this.cluster_.getBounds());"

Original comment by victoryi...@gmail.com on 16 Jun 2011 at 3:52

[GoogleCodeExporter]

I've found a workaround for this issue after a bit of play. I found that if you 
specify the url of your custom cluster styles using an absolute url (e.g. 
https://hostname/bar.jpg) then this error does not occur. A relative url (e.g. 
/bar.jpg) will result in this issue. This will work for me, for now, but I hope 
to be able to again use relative urls at some point.

Original comment by ncj...@gmail.com on 16 Jun 2011 at 6:04

[GoogleCodeExporter]

Nice! Thanks for the quick workaround!!! The absolute URL will def cause some 
problems for me since our URL changes per environment ex: (dev.hostname), 
(qa.hostname). But at least it works! Hopefully the issue can be resolved, 
thanks again!

Original comment by victoryi...@gmail.com on 16 Jun 2011 at 6:33

[GoogleCodeExporter]

I have exactly the same problem. I've decided to prepend the host and protocol 
of the current page in javascript to the relative urls. Here's what I ended up 
with:

var absolutePath = window.location.protocol + "//" + window.location.host;

var styles = [{ url: absolutePath + "/my/absolute/path.jpg",
...

Original comment by ncj...@gmail.com on 16 Jun 2011 at 8:16

[GoogleCodeExporter]

You my friend deserve a cookie... Works like a charm! I did something similar 
but overlooked the window.location.protocol, so that will be a nice addition. 
Thanks for all the input and help!

Original comment by victoryi...@gmail.com on 16 Jun 2011 at 10:12

[GoogleCodeExporter]

This solves the problem for me too

Original comment by petrusgo...@gmail.com on 5 Nov 2012 at 4:59