Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
dglux5_wiki:widgets_and_property_inspector:components:iframe:home [2020/01/10 20:50]
itsarev
dglux5_wiki:widgets_and_property_inspector:components:iframe:home [2020/01/30 17:05] (current)
itsarev [Troubleshooting]
Line 85: Line 85:
 If you try to load HTTP content using IFrame on HTTPS DGLux installation,​ browsers including Chrome do not allow such thing by default. It is not secure to load HTTP content via an HTTPS connection since that content might be compromised. So for the IFrame to work properly you need to load it from a server with HTTPS. If you try to load HTTP content using IFrame on HTTPS DGLux installation,​ browsers including Chrome do not allow such thing by default. It is not secure to load HTTP content via an HTTPS connection since that content might be compromised. So for the IFrame to work properly you need to load it from a server with HTTPS.
  
-Another potential obstacle is **Origin Policy** which browser has to follow. Some domains (for example, google.com) send a header **X-Frame-Options** that disallows ​loading a page in an IFrame from the domain different from the origin. However some of the web services are more “friendly",​ for example Youtube. So basically you need to make sure that web server of the page you’re trying to load doesn’t send such a header. Use Developer Tools in Chrome to see all the error messages related to that.+Another potential obstacle is **Origin Policy** which browser has to follow. Some domains (for example, google.com) send a header **X-Frame-Options** that disallow ​loading a page in an IFrame from the domain different from the origin. More on this topic [[https://​developer.mozilla.org/​en-US/​docs/​Web/​HTTP/​Headers/​X-Frame-Options|here]]. Howeversome of the web services are more “friendly",​ for exampleYoutube. So basically you need to make sure that the web server of the page you’re trying to load doesn’t send such a header. Use Developer Tools in Chrome to see all the error messages related to that.
  
 ---- ----