# Perspective IFrame Component

**URL:** <https://forum.inductiveautomation.com/t/perspective-iframe-component/56218>\
**Category:** Ignition\
**Created:** [February 16, 2022, 4:40pm UTC](https://forum.inductiveautomation.com/t/perspective-iframe-component/56218 "2022-02-16T16:40:54Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![jacob.ramirez](https://avatars.discourse-cdn.com/v4/letter/j/9dc877/32.png) [@jacob.ramirez](https://forum.inductiveautomation.com/u/jacob.ramirez)\
**Post date:** [February 16, 2022, 4:40pm UTC](https://forum.inductiveautomation.com/t/perspective-iframe-component/56218/1 "2022-02-16T16:40:54Z")

</div>

How does the endpoint view the IFrame component?

For example, if the server sees the IFrame component request come from our Ignition server? Or from the user’s perspective session?

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [February 16, 2022, 4:42pm UTC](https://forum.inductiveautomation.com/t/perspective-iframe-component/56218/2 "2022-02-16T16:42:05Z")

</div>

It’s just a browser iframe element; we’re not doing anything special to pipe it through the gateway.  
You will only have access (from your browser/mobile device/workstation) if you would have access otherwise.

---

<div class="post-metadata">

**Author:** ![jacob.ramirez](https://avatars.discourse-cdn.com/v4/letter/j/9dc877/32.png) [@jacob.ramirez](https://forum.inductiveautomation.com/u/jacob.ramirez)\
**Post date:** [February 16, 2022, 4:44pm UTC](https://forum.inductiveautomation.com/t/perspective-iframe-component/56218/3 "2022-02-16T16:44:12Z")

</div>

So if the endpoint we want the iframe to use only allows a certain IP address (Gateway IP Address), the perspective clients wouldn’t receive a response?

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [February 16, 2022, 4:46pm UTC](https://forum.inductiveautomation.com/t/perspective-iframe-component/56218/4 "2022-02-16T16:46:59Z")

</div>

That’s correct. If you wouldn’t be able to see it in a normal webpage, you definitely won’t be able to see it via the iframe.

---

<div class="post-metadata">

**Author:** ![jacob.ramirez](https://avatars.discourse-cdn.com/v4/letter/j/9dc877/32.png) [@jacob.ramirez](https://forum.inductiveautomation.com/u/jacob.ramirez)\
**Post date:** [February 16, 2022, 4:48pm UTC](https://forum.inductiveautomation.com/t/perspective-iframe-component/56218/5 "2022-02-16T16:48:42Z")

</div>

Got it. Thank you.

---

<div class="post-metadata">

**Author:** ![jacob.ramirez](https://avatars.discourse-cdn.com/v4/letter/j/9dc877/32.png) [@jacob.ramirez](https://forum.inductiveautomation.com/u/jacob.ramirez)\
**Post date:** [February 16, 2022, 8:06pm UTC](https://forum.inductiveautomation.com/t/perspective-iframe-component/56218/6 "2022-02-16T20:06:07Z")

</div>

If I had a video feed coming into the same server as the Ignition server (or one on the same network), any suggestions on how I would go about accessing the feed through an Ignition HMI and the connection not coming from the user’s perspective session, the connection has to come from the server?

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [February 16, 2022, 8:14pm UTC](https://forum.inductiveautomation.com/t/perspective-iframe-component/56218/7 "2022-02-16T20:14:04Z")

</div>

I would look into a reverse proxy (e.g nginx, Traefik). You run it on the same host and it transparently rewrites incoming requests to other services on different ports, or even entirely different machines.