# Inline Frame Component unable to access most URLs **URL:** \ **Category:** Ignition\ **Created:** [October 15, 2019, 5:41am UTC](https://forum.inductiveautomation.com/t/inline-frame-component-unable-to-access-most-urls/29085 "2019-10-15T05:41:25Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![Andrew.Zebic](https://avatars.discourse-cdn.com/v4/letter/a/a183cd/32.png) [@Andrew.Zebic](https://forum.inductiveautomation.com/u/Andrew.Zebic)\ **Post date:** [October 15, 2019, 5:41am UTC](https://forum.inductiveautomation.com/t/inline-frame-component-unable-to-access-most-urls/29085/1 "2019-10-15T05:41:25Z")
Hi, I’m trying to use the inline frame component, and it doesn’t seem to work with most url’s. While I can access localhost:8088 or [https://www.youtube.com/embed/hYXUZeLw5ek](https://www.youtube.com/embed/hYXUZeLw5ek) (given in the inline frame example), I haven’t been able to reach any others. Is there something I’m missing regarding the component? Naturally adjusting the referrer policy hasn’t changed anything either. Regards, Andrew. ---
**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:** [October 16, 2019, 4:07pm UTC](https://forum.inductiveautomation.com/t/inline-frame-component-unable-to-access-most-urls/29085/2 "2019-10-16T16:07:36Z")
There’s currently an issue with the referrer policy you set not actually being used on the page, but the main drawback to iframes is that _many_ websites will not support rendering if they’re inside a frame. This is done via the [`x-frame-options`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Frame-Options) HTTP header, which [all browsers support](https://caniuse.com/#feat=x-frame-options). If a given page returns a `DENY` or `SAMEORIGIN` value for `x-frame-options`, then your web browser will refuse to render the content inside the iframe component in your Perspective page. There’s nothing we can do to change that - the entire point of `x-frame-options` is to (help) prevent a class of web security attacks called [clickjacking](https://en.wikipedia.org/wiki/Clickjacking). ---
**Author:** ![hunterdg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/hunterdg/32/67774_2.png) [@hunterdg](https://forum.inductiveautomation.com/u/hunterdg)\ **Post date:** [November 6, 2020, 4:02am UTC](https://forum.inductiveautomation.com/t/inline-frame-component-unable-to-access-most-urls/29085/3 "2020-11-06T04:02:21Z")
Is there an easy method to allow the exact opposite (embedding ignition views in iframes)? I know how to modify header filter in tomcat, but from googling, seems I’m a bit over my head re: Jetty ---
**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:** [November 6, 2020, 3:23pm UTC](https://forum.inductiveautomation.com/t/inline-frame-component-unable-to-access-most-urls/29085/4 "2020-11-06T15:23:24Z")
[https://docs.inductiveautomation.com/display/DOC80/Gateway+Configuration+File+Reference#GatewayConfigurationFileReference-XFrameOptions](https://docs.inductiveautomation.com/display/DOC80/Gateway+Configuration+File+Reference#GatewayConfigurationFileReference-XFrameOptions) ---
**Author:** ![hunterdg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/hunterdg/32/67774_2.png) [@hunterdg](https://forum.inductiveautomation.com/u/hunterdg)\ **Post date:** [November 6, 2020, 3:50pm UTC](https://forum.inductiveautomation.com/t/inline-frame-component-unable-to-access-most-urls/29085/5 "2020-11-06T15:50:59Z")
thanks, apologies for not RTFM ---
**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:** [November 6, 2020, 3:52pm UTC](https://forum.inductiveautomation.com/t/inline-frame-component-unable-to-access-most-urls/29085/6 "2020-11-06T15:52:26Z")
It’s a big manual, and those overrides are a fairly recent feature 🙂 ---
**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:** [September 28, 2022, 1:30pm UTC](https://forum.inductiveautomation.com/t/inline-frame-component-unable-to-access-most-urls/29085/7 "2022-09-28T13:30:09Z")
I made changes to my ignition.conf file, I added `wrapper.java.additional.4=-Dignition.http.header.x_frame_options.enabled=false wrapper.java.additional.5=-Dignition.http.header.x_frame_options.value=SAMEORIGIN ` then restarted the gateway and the same result. I’ve been trying with [https://www.google.com/](https://www.google.com/) with no luck. Are there any other changes that need to be made to get the iFrame to work? ---
**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:** [September 28, 2022, 1:33pm UTC](https://forum.inductiveautomation.com/t/inline-frame-component-unable-to-access-most-urls/29085/8 "2022-09-28T13:33:59Z")
These change the headers returned by the Ignition Gateway, and only affect your ability to embed the gateway/Perspective pages in an iframe. Google’s landing page doesn’t allow itself to be embedded in an iframe, you can’t work around that, and so it doesn’t make a good test candidate. What are you trying to achieve in the end here? ---
**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:** [September 28, 2022, 1:36pm UTC](https://forum.inductiveautomation.com/t/inline-frame-component-unable-to-access-most-urls/29085/9 "2022-09-28T13:36:35Z")
In the long run, some sort of remote camera stream (which is a nightmare to figure out) but at the moment I can bring up the camera web page in my web browser but in the iFrame it doesn’t work. ---
**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:** [September 28, 2022, 1:38pm UTC](https://forum.inductiveautomation.com/t/inline-frame-component-unable-to-access-most-urls/29085/10 "2022-09-28T13:38:22Z")
There’s a couple reasons this might not work. Most common would be that the camera is accessed by HTTP but you are using HTTPS to view Perspective pages. You can’t embed unsecured content into a secured page. End of story. Second would be that the camera is serving up pages with headers that prevent it. You’d have to be able to make a configuration change on the camera’s web server, not Ignition, to change this. ---
**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:** [September 28, 2022, 1:41pm UTC](https://forum.inductiveautomation.com/t/inline-frame-component-unable-to-access-most-urls/29085/11 "2022-09-28T13:41:32Z")
If the problem is the first, and the camera feeds can’t be secured, a workaround is to put a reverse proxy (nginx etc…) that _does_ have HTTPS enabled in front of all the unsecured cameras. ---
**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:** [September 28, 2022, 5:27pm UTC](https://forum.inductiveautomation.com/t/inline-frame-component-unable-to-access-most-urls/29085/12 "2022-09-28T17:27:47Z")
I moved the screen with the iFrame to the Ignition system that I use https on. Now I’m not sure what headers would be preventing it and how to view them. ---
**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:** [September 28, 2022, 5:48pm UTC](https://forum.inductiveautomation.com/t/inline-frame-component-unable-to-access-most-urls/29085/13 "2022-09-28T17:48:21Z")
I got this working finally. I had to use the markdown component to get it working. ---
**Author:** ![mwd123](https://avatars.discourse-cdn.com/v4/letter/m/ea666f/32.png) [@mwd123](https://forum.inductiveautomation.com/u/mwd123)\ **Post date:** [December 13, 2022, 10:27am UTC](https://forum.inductiveautomation.com/t/inline-frame-component-unable-to-access-most-urls/29085/14 "2022-12-13T10:27:14Z")
I know this is an old thread, but how did you do it with markdown? Can you paste the code please? BR /M ---
**Author:** ![yin.cheng](https://avatars.discourse-cdn.com/v4/letter/y/85f322/32.png) [@yin.cheng](https://forum.inductiveautomation.com/u/yin.cheng)\ **Post date:** [June 12, 2024, 7:27am UTC](https://forum.inductiveautomation.com/t/inline-frame-component-unable-to-access-most-urls/29085/15 "2024-06-12T07:27:02Z")
Hi Jacob, do you mind sharing how did you managed to get it working by using the markdown component? ---
**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:** [June 12, 2024, 1:12pm UTC](https://forum.inductiveautomation.com/t/inline-frame-component-unable-to-access-most-urls/29085/16 "2024-06-12T13:12:06Z")
I ended up using an iFrame, at one point I got something to work with a markdown, which was an iFrame, it had the \