# Questions about Inline frame

**URL:** <https://forum.inductiveautomation.com/t/questions-about-inline-frame/96347>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [September 24, 2024, 9:18am UTC](https://forum.inductiveautomation.com/t/questions-about-inline-frame/96347 "2024-09-24T09:18:51Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Senthee\_Wu](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/senthee_wu/32/67770_2.png) [@Senthee\_Wu](https://forum.inductiveautomation.com/u/Senthee_Wu)\
**Post date:** [September 24, 2024, 9:18am UTC](https://forum.inductiveautomation.com/t/questions-about-inline-frame/96347/1 "2024-09-24T09:18:51Z")

</div>

Hi everyone, I'm having problems with **Inline Frame** , I've looked through the forums and haven't found anyone sharing a similar problem to mine.

I put a frontend interface A on **Inline Frame** , after saving the project and opening it in a browser, it shows the login page for A. After entering my password and clicking login, I can't jump to the homepage of A. I'm having trouble with this.

I checked the developer platform of the browser and the interface to verify the password is triggered successfully after clicking the login button.

What should I do next to troubleshoot the next problem, I have no clue, what I can confirm is that X-Frame-Options is not set to be disabled on A's system.

---

<div class="post-metadata">

**Author:** ![Senthee\_Wu](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/senthee_wu/32/67770_2.png) [@Senthee\_Wu](https://forum.inductiveautomation.com/u/Senthee_Wu)\
**Post date:** [September 24, 2024, 10:08am UTC](https://forum.inductiveautomation.com/t/questions-about-inline-frame/96347/3 "2024-09-24T10:08:33Z")

</div>

Maybe there's something wrong with my statement that System A doesn't use X-Frame-Options, so his login page can be displayed normally instead of showing refused to connect. and I do see in the developer tool of my browser that this is not used.

I think it should be something else.

---

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [September 24, 2024, 11:42am UTC](https://forum.inductiveautomation.com/t/questions-about-inline-frame/96347/4 "2024-09-24T11:42:09Z")

</div>

OK. I misunderstood. I'll delete my previous post as it's not relevant.

---

<div class="post-metadata">

**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:** [September 24, 2024, 12:42pm UTC](https://forum.inductiveautomation.com/t/questions-about-inline-frame/96347/5 "2024-09-24T12:42:54Z")

</div>

X-Frame-Options must be affirmatively set to to allow IFrame usage. Missing the option is equivalent to disallowing IFrames, IIRC.

---

<div class="post-metadata">

**Author:** ![Senthee\_Wu](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/senthee_wu/32/67770_2.png) [@Senthee\_Wu](https://forum.inductiveautomation.com/u/Senthee_Wu)\
**Post date:** [September 25, 2024, 2:09am UTC](https://forum.inductiveautomation.com/t/questions-about-inline-frame/96347/6 "2024-09-25T02:09:48Z")

</div>

I just added it, but it still doesn't jump from the login page to the home page

 ![img_v3_02f2_8d50fb63-053f-4694-a7db-3c60eec9a3cg](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/6/168ca74abbe7abc04276f1a2a584942415ff3098.jpeg)

---

<div class="post-metadata">

**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:** [September 25, 2024, 12:03pm UTC](https://forum.inductiveautomation.com/t/questions-about-inline-frame/96347/7 "2024-09-25T12:03:07Z")

</div>

"Same Origin" means the IFrame must be delivered by the same server to be allowed. That is the default that prevents other servers from embedding the content in their IFrame.

---

<div class="post-metadata">

**Author:** ![Senthee\_Wu](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/senthee_wu/32/67770_2.png) [@Senthee\_Wu](https://forum.inductiveautomation.com/u/Senthee_Wu)\
**Post date:** [September 25, 2024, 12:20pm UTC](https://forum.inductiveautomation.com/t/questions-about-inline-frame/96347/8 "2024-09-25T12:20:23Z")

</div>

Sorry I didn't understand carefully, so how do I change this configuration please.

Someone just told me that it's because the token is not being passed, but I don't know if it is, do you understand what it means?

---

<div class="post-metadata">

**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:** [September 25, 2024, 12:24pm UTC](https://forum.inductiveautomation.com/t/questions-about-inline-frame/96347/9 "2024-09-25T12:24:58Z")

</div>

See the docs here:

> **[X-Frame-Options - HTTP | MDN](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options)**
>
> The X-Frame-Options HTTP response header can be used to indicate whether a browser should be allowed to render a page in a ,

You need the "Allow-From ..." syntax that explicitly identifies the system that will wrap around the IFrame. But note the compatibility warning that recommends using Content-Security-Policy.

---

<div class="post-metadata">

**Author:** ![victordcq](https://avatars.discourse-cdn.com/v4/letter/v/f6c823/32.png) [@victordcq](https://forum.inductiveautomation.com/u/victordcq)\
**Post date:** [September 25, 2024, 3:00pm UTC](https://forum.inductiveautomation.com/t/questions-about-inline-frame/96347/10 "2024-09-25T15:00:44Z")

</div>

Allow all is the default if nothing is filled in normally.  
So that was not what the initial problem was
