# Grafan ifram in Perspective Page

**URL:** <https://forum.inductiveautomation.com/t/grafan-ifram-in-perspective-page/104296>\
**Category:** Ignition\
**Created:** [March 27, 2025, 11:52am UTC](https://forum.inductiveautomation.com/t/grafan-ifram-in-perspective-page/104296 "2025-03-27T11:52:56Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [March 27, 2025, 12:08pm UTC](https://forum.inductiveautomation.com/t/grafan-ifram-in-perspective-page/104296/4 "2025-03-27T12:08:39Z")

</div>

> [@Show http URL in Iframe in Perspective](https://forum.inductiveautomation.com/t/show-http-url-in-iframe-in-perspective/65747/5):
>
> This is generally not allowed by browsers: [Mixed content - Web security | MDN](https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content) My usual recommendation is to put reverse proxy that has HTTPS enabled in front of legacy resources that can't be upgraded to use HTTPS.

---

_[View the full topic](https://forum.inductiveautomation.com/t/grafan-ifram-in-perspective-page/104296)._