Welcome Guest Search | Active Topics | Sign In | Register

Mixed content (secured & non secured) issue with the progressbar Options
Abdu
Posted: Monday, February 21, 2011 2:18:00 PM
Rank: Member
Groups: Member

Joined: 9/1/2010
Posts: 28
I have a similar issue with the issue mentioned in this post. IE pops up a warning about mixed content of secured and non secured when using https with a page containing a progressbar control. Removing the progressbar removed the warning. That's how I figured the progressbar is causing the issue. Plus the fact that the progressbar creates an iframe.

This Stackoverflow question mentions that an empty iFrame causes the warning in IE. I don't experience this issue with Chrome, Firefox and Opera, the other non IE I tested with.

As a test I tried saving the page's html complete source, manipulate the iFrame and serve it using https from my machine but I got several javascript errors so I abandoned this method.

My app uses IE7 compatibility mode (for some other issue). My workaround was for this page which has the warning issue, I had it render in standards mode. The warning disappeared.

I am not sure if this is an IE issue, EO or both. My guess is that EO is rendering the iFrame in a manner which IE doesn't like... in a certain IE mode.

I am posting this for the user as a helpful hint where switching IE's mode can solve the issue and for EO developers to maybe look further into iFrame rendering.
eo_support
Posted: Monday, February 21, 2011 3:10:22 PM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,194
Hi,

Thank you very much for the information. The empty iframe issue is already correctly handled by the ProgressBar (The ProgressBar actually renders an iframe with a valid src attribute, so it does not causes the SSL warning message). So it is not the iframe issue alone. The original post you mentioned was traced back to the user's CSS file.

We are unable to reproduce the problem in IE 7, IE 8 or IE 8 compatible view. If you have a test page that can reproduce the problem, please share with us. Also please include the exact steps to reproduce the problem. We can not guarantee that it will be resolved because we do not know what's causing the problem yet or whether it's a browser issue yet. However we will be happy to look into it as soon as we have a test page that can reproduce the problem.

Thanks!


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.