Network Management
Webpage created from Engineers Toolset published to the Orion server will not display in iFrame custom HTML
If you have created a Customer Webpage from the Engineers Toolset and published to the Orion server and set up as an iFrame, stops working, even though it has worked for a long time, you may find this article helpful.
First published date
Last published date
Overview
Example:
If you have SolarWinds Engineers Toolset, there is an option to create custom gauges and upload the webpage to a website. For ease of access you may want hosted of the Orion Server.
It's important to understand that you shouldn't attempt to mix HTTPs and HTTP in an iFrame:
Why you should not mix http and https when using iframes
January 7, 2017 by TinyWebGallery In the administration of advanced iframe I have written the following note: "Please do not use a different protocol for the iframe: Do not mix http and https if possible!".What does this mean?
- If the protocol of your page is http than use a http page inside the iframe.
- If the protocol of your page is https than use a https page inside the iframe.
But why should you not do this?
1. https with http iframe Lets start with the one you can not do: Your page is https and your iframe page is http. This scenario is called "Mixed Active Content" and is blocked by all major browsers now. You can open this test page and check the browser console (F12) for the errors you get then! -> HTTP pages cannot be included directly into HTTPS pages! 2. http with https iframe -> HTTPS pages can be included into HTTP pages! What you can do is including an iframe with a https page into a http page. This not recommended as is generally bad practice to embed an iframe with content served over HTTPS within a page served over plain HTTP (or mix content). The reason for this is, that there's no good way for the user to check they're using the HTTPS site they intend (unless the user really wants to check the source of the page). They also don't know that e.g. their login credentials are sent over HTTPS as in the browser address only HTTP is visible. Also you need to try if your pages are working on all major browsers. I already had users with side effects when it comes to cookies or session handling! My recommendation is to upgrade your http page to https! IF YOU STILL WANT TO DO THIS: The external workaround is by default NOT working in this setup as the Javascript is than loaded from an http domain which is blocked! To get this working in the pro version you need to- Enable "Use post message for communication" on the "External workaround" tab.
- Copy the generated ai_external.js to a https domain and include it from there! Remember to copy the ai_external.js each time you change something with the "save" icon in the administration.
(Copyright © 2020 TinyWebGallery Blog, available at https://www.tinywebgallery.com/blog/iframe-do-not-mix-http-and-https , obtained on 11/12/2020)
Product section
Cause
Resolution
Workaround
Try publishing the webpage, or putting the location of the webpage withing the Orion Website folders.Example:
- Pubilsh to C:\inetpub\SolarWinds\Orion\Charts\Bandwidth.htm
- Then browse to http://[FQDN]/Orion/Charts/bandwidth.htm
- If that works place the URL into the iframe for the custom HTML widget
https://support.solarwinds.com/SuccessCenter/s/article/Create-custom-HTML-resource-view