"only secure content is displayed" displayed when using IE

[QGTFS]

Hello Qlik community,

We're currently using the version 12.90.2 of Qlikview, using only one server.

When opening a report with qvplugin in edge, with compatibility with internet explorer, a small popup appears at the bottom of the page with the following prompt: only secure content is displayed.

Requiring to allow it, every time we access it this way, and it seem to not appear even for some users, thus not having access to the report.

We're using https and tried to follow the instructions from this knowledge case :

https://support.qlik.com/articles/000070197

https://community.qlik.com/t5/QlikView-Administration/In-IE-9-we-get-the-message-at-the-bottom-of-th...

Yet, the pop up still appears, I've also tried to tinker with internet options to see if it was related to the primary security parameters. Unfortunately, even with all prompt changed to "enable", the pop up still shows up with this configuration.

A possibility, is that it would be certificate related, as internet explorer mode (after selecting show all content, not the case before this) does not consider the website secure, even if it is considered secured using ajax instead of qvplugin.

Has anyone encountered this issue before ? 

[QGTFS]

Hello, has someone a clue about this topic by any chance? I haven't found more info on the subject so far. 

[marcus_sommer · Accepted solution]

Does this also happens without the plugin and/or in another browser?

Further, does the issue occur with a complete new created qvw (not based on any template - pure) without any UI object? The next might be to add there a list-box and table-chart on some dummy-records and after it maybe some more stuff - does anything change or being unexpected?

Possible causes may be that any extension, action, embedded urls/pictures and so on may come per http or another not trusted domain or missing/invalide certificates or similar stuff - maybe also through any proxies or re-directs.

[QGTFS]

Hi Marcus, thank you very much for your answer ! 

It only happens with the plugin in edge with IE compatibility. The ajax versions work fine.

Thank you for the advice ! Indeed, I don't have the issue on an empty document. I'll continue to investigate and post if I find anything else.