iframe does not display.
On page with 3 iframes, first iframe displays, the next two do not. Firefox on Linux. Chrome displays all three iframes. Firefox on Android displays all three iframes. On Linux, Save Page to disk, and then run the html off of disk, and all three iframes display!!!
선택된 해결법
Yes, unlike HTTP images in an HTTPS page, which are allowed through with a little warning on the padlock, iframes are considered potentially dangerous active content and HTTP iframes won't be loaded into an HTTPS page -- and the cross-site aspect probably isn't helping.
When you saved the main document to a local file, the more lax rules for the FILE protocol were applied.
If this is your site, try to standardize the protocols.
문맥에 따라 이 답변을 읽어주세요 👍 2모든 댓글 (7)
Can you provide a link to the problem page, assuming it's appropriate for a public forum?
You could check for messages in Firefox's Web Console. You can open the Web Console in the lower part of the tab using either:
- "3-bar" menu button > Developer > Web Console
- (menu bar) Tools > Web Developer > Web Console
- (Windows) Ctrl+Shift+k
Then reload the page in the upper part of the tab and watch for error or security messages. (The lines with blue triangles generally are not significant unless you suspect a style rule problem.) Anything that sounds like it could be relevant?
web console Blocked loading mixed active content “http://stage48.net/studio48/fukyouwaon.html”[Learn More]
fpp004.html
Blocked loading mixed active content “http://takahirony.com/”[Learn More] fpp004.html
my comment:
youtube frame is https but the other two are http. I assume that is the complaint from my Firefox on Linux.
Thanks for your help. At least I understand the problem. Its a security issue. But I would have expected that Firefox on Android would behave in the same way. We can end this now. Thanks again.
선택된 해결법
Yes, unlike HTTP images in an HTTPS page, which are allowed through with a little warning on the padlock, iframes are considered potentially dangerous active content and HTTP iframes won't be loaded into an HTTPS page -- and the cross-site aspect probably isn't helping.
When you saved the main document to a local file, the more lax rules for the FILE protocol were applied.
If this is your site, try to standardize the protocols.
Once again thank you very much. This makes a whole lotta sense. Bringing a http page into a https page, compromises the security and is exploitable. Natch. But I am still bothered that Firefox on my Android mobile device does allow this! I would think that they should work alike. But thanks again. KK
John1590 said
But I am still bothered that Firefox on my Android mobile device does allow this! I would think that they should work alike.
They should, if the protocol (HTTP vs. HTTPS) is identical on both devices. (I don't see the second and third frames if I use HTTPS on Fx/Android.)