NYCPHP Meetup

[Hans Zaunere]

Jeff wrote:

> I believe there is a known bug in IE that, when using https, it has
> difficulty resolving objects (images, links) if they use relative paths
> so a user can sometimes see a message that says there are secure and
> insecure items on a page. The workaround, as I understand it, is to use
> a full path to the object(s). The question is, then, whether the path
> should be something like "/index.php" or does IE prefer
> "https://mydomain.com/index.php" ?

I have no idea whether this is the correct solution, but is the only one I've been able to find in the wide world of browsers.  I had to hack https:// into a bunch of CF code (only for images, however) at one point, because of this.

H