# Inline/IFrame between Ignition Gateways **URL:** \ **Category:** Ignition\ **Tags:** perspective, ignition83\ **Created:** [July 3, 2026, 5:07am UTC](https://forum.inductiveautomation.com/t/inline-iframe-between-ignition-gateways/116257 "2026-07-03T05:07:27Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![eab](https://avatars.discourse-cdn.com/v4/letter/e/e47c2d/32.png) [@eab](https://forum.inductiveautomation.com/u/eab)\ **Post date:** [July 3, 2026, 5:07am UTC](https://forum.inductiveautomation.com/t/inline-iframe-between-ignition-gateways/116257/1 "2026-07-03T05:07:27Z")
How do you use an Inline Frame (Iframe) from a Frontend Gateway to embed a Backend Gateway Perspective view? I've looked through the documentation and watched several videos, but I haven't been able to find any examples of how to do this. My goal is to display a Perspective session hosted on a Backend Gateway inside a Frontend Gateway using an Inline Frame component. **Example:** - Frontend Gateway: `http://1.1.1.1:8088` - Backend Gateway: `http://2.2.2.2:8088` I would like to embed the following Backend Perspective session inside a view on the Frontend Gateway: (http://)2.2.2.2:8088/data/perspective/client/Main Is this a supported approach, and if so, are there any special configuration requirements regarding authentication, security zones, or cross-origin restrictions? Any examples or step by step guides would be appreciated. Thanks! ---
**Author:** ![Cose\_Peter1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cose_peter1/32/79174_2.png) [@Cose\_Peter1](https://forum.inductiveautomation.com/u/Cose_Peter1)\ **Post date:** [July 3, 2026, 6:02am UTC](https://forum.inductiveautomation.com/t/inline-iframe-between-ignition-gateways/116257/2 "2026-07-03T06:02:32Z")
> [@eab](#): > > (http://)2.2.2.2:8088/data/perspective/client/Main Any errors while doing this? ---
**Author:** ![eab](https://avatars.discourse-cdn.com/v4/letter/e/e47c2d/32.png) [@eab](https://forum.inductiveautomation.com/u/eab)\ **Post date:** [July 3, 2026, 6:39am UTC](https://forum.inductiveautomation.com/t/inline-iframe-between-ignition-gateways/116257/3 "2026-07-03T06:39:52Z")
I just created a container session to show it: Networks are connected between them. 8090 is this session. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/b/7b8b781ceac6cfa304d1fe0a1c14375b659ac06f.png) 8092 different session ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/1/912faa0bfa1cb25eed52339002dfb300daa4995c.png) And then i tried the view i created on 8090 session: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/2/52a475fc17baf1d1fbc9b776b656780902d0f5c4.png) And the headers show this: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/2/325cce95ddab2d0d9a540cf7172fa359d9dbf343.png) ---
**Author:** ![Cose\_Peter1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cose_peter1/32/79174_2.png) [@Cose\_Peter1](https://forum.inductiveautomation.com/u/Cose_Peter1)\ **Post date:** [July 3, 2026, 7:29am UTC](https://forum.inductiveautomation.com/t/inline-iframe-between-ignition-gateways/116257/4 "2026-07-03T07:29:19Z")
From what I read, the header response ``` ```python X-Frame-Options: SAMEORIGIN ``` makes the browser block it. I'm not sure if this can be disabled. ---
**Author:** ![eab](https://avatars.discourse-cdn.com/v4/letter/e/e47c2d/32.png) [@eab](https://forum.inductiveautomation.com/u/eab)\ **Post date:** [July 3, 2026, 7:45am UTC](https://forum.inductiveautomation.com/t/inline-iframe-between-ignition-gateways/116257/5 "2026-07-03T07:45:57Z")
Yea, i came to the same conclusion. I was hoping maybe some experts had found a way to work around it to make it work. ---
**Author:** ![william.bowen](https://avatars.discourse-cdn.com/v4/letter/w/8c91f0/32.png) [@william.bowen](https://forum.inductiveautomation.com/u/william.bowen)\ **Post date:** [July 3, 2026, 7:59am UTC](https://forum.inductiveautomation.com/t/inline-iframe-between-ignition-gateways/116257/6 "2026-07-03T07:59:38Z")
You'll need to disable the [X-Frame-Options](https://docs.inductiveautomation.com/docs/8.3/appendix/reference-pages/gateway-configuration-file-reference/gateway-and-gateway-network-parameters#x-frame-options) header in your Gateway Configuration File. Like this, where the # needs to not conflict with any other parameters listed in that file, [see here](https://docs.inductiveautomation.com/docs/8.3/appendix/reference-pages/gateway-configuration-file-reference#changing-java-additional-parameters): `wrapper.java.additional.#=-Dignition.http.header.x_frame_options.enabled=false` This requires a gateway restart once you Java Additional Parameter. ---
**Author:** ![eab](https://avatars.discourse-cdn.com/v4/letter/e/e47c2d/32.png) [@eab](https://forum.inductiveautomation.com/u/eab)\ **Post date:** [July 3, 2026, 8:48am UTC](https://forum.inductiveautomation.com/t/inline-iframe-between-ignition-gateways/116257/7 "2026-07-03T08:48:57Z")
Yes it seems like this did the trick, thank you. I am at least one step closer now: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/f/6fa76fed18a69fb81cb912c8f9bddb91ce5e5c1c.jpeg) I can add that this is where you edit the ignition.conf file if you have selected the standard install format: C:\Program Files\Inductive Automation\Ignition\data ---
**Author:** ![william.bowen](https://avatars.discourse-cdn.com/v4/letter/w/8c91f0/32.png) [@william.bowen](https://forum.inductiveautomation.com/u/william.bowen)\ **Post date:** [July 3, 2026, 9:33am UTC](https://forum.inductiveautomation.com/t/inline-iframe-between-ignition-gateways/116257/8 "2026-07-03T09:33:32Z")
If its stuck on Initializing Client, I believe you'll have to setup SSL on these gateway and use HTTPS instead, then add 2 more parameters into the configuration file: `wrapper.java.additional.#=-Dignition.http.session.cookie.same-site.enabled=true` `wrapper.java.additional.#=-Dignition.http.session.cookie.same-site.value=None` This can be done with a [self signed certification](https://docs.inductiveautomation.com/docs/8.3/platform/gateway/web-interface/network/web-server-settings/secure-communication-ssl-tls#how-to-install-a-self-signed-certificate). If this is you first time setting up SSL in Ignition I recommended not to enable the **Force Secure Redirect** option in the Web Server settings, by leaving this off you will still be able to access the gateway incase the SSL setup doesn't work. For testing you can use localhost as the domain on the self signed certificate, otherwise you can add a IP address down in the Subject Alternative Names. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [July 3, 2026, 12:10pm UTC](https://forum.inductiveautomation.com/t/inline-iframe-between-ignition-gateways/116257/9 "2026-07-03T12:10:17Z")
Be aware that the end-user's browser now has to reach both gateways, and your front-end isn't reducing the workload on the backend as would be expected. The canonical solution would be to use a remote tag provider or MQTT to move live data to the front end so the front end can display the view directly.