# Inline Frame Component unable to access most URLs

**URL:** <https://forum.inductiveautomation.com/t/inline-frame-component-unable-to-access-most-urls/29085>\
**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:** 1\
**Showing post:** 8

<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:** [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")

</div>

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?

---

_[View the full topic](https://forum.inductiveautomation.com/t/inline-frame-component-unable-to-access-most-urls/29085)._