Hello Christian,
this is likely due to the MIXED_CONTENT policy in modern browser: if you are accessing a page via HTTPS it is not (directly) possible to embed an iframe using an HTTP address.
See for instance https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content for an explanation.
The solution would be to access the external page using https.
Best,
Andreas
--
You received this message because you are subscribed to the Google Groups "Information Workbench Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
iwb-discussio...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi Christian,
for security reasons HTTP needs to be explicitly enabled (i.e. it is not available by default), see https://help.fluidops.com/resource/Help:Installation#Enabling_HTTP
Note that this can be set on “/resource/Admin:Config” (search for enableHttp) and that the setting requires a restart.
Hi Christian,
we just locally tested this and for us enabling HTTP works with the following steps
1) put “enableHttp=true” into config.prop (or change it in the UI)
2) restart the platform
3) Check in the logs that you see something like
--
Andreas Schwarte
Platform Architect
T +49 6227 3580 87 – 40
fluid Operations AG | Altrottstrasse 31 | 69190 Walldorf | Germany | www.fluidops.com
fluidOps – Semantifying Business
Executive Board Paul Bolger | Supervisory Board Michelle VonderHaar, Larry Martin, Keith Morrow | Register Court Mannheim, HRB 709796 | VAT-No. DE258759786
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
For completeness the rest of the mail
we just locally tested this and for us enabling HTTP works with the following steps
1) put “enableHttp=true” into config.prop (or change it in the UI)
2) restart the platform
3) Check in the logs that you see something like
2018-03-12 09:08:41,244 INFO [serviceMain] com.fluidops.jetty.StartJetty - HTTP URL: http://xx.xx.xx.xx:50080
4) navigate to http://localhost:50080/
Can you check if any firewall prevents the access?
Best,
Andreas
Hi Christian,
as an Iframe renders an external source it is (generally) not possible to modify its content. This is particularly true if the content is not provided by the same web-server.
If you want to modify the content of the iframe (e.g. via styling) you have to do this in the source.
In the platform you can modify the iframe itself, e.g. adding a border.