# Extracting HTML Source Code from Inline Frame

**URL:** <https://forum.inductiveautomation.com/t/extracting-html-source-code-from-inline-frame/75481>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [June 23, 2023, 9:15pm UTC](https://forum.inductiveautomation.com/t/extracting-html-source-code-from-inline-frame/75481 "2023-06-23T21:15:52Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Derek\_Phillips](https://avatars.discourse-cdn.com/v4/letter/d/779978/32.png) [@Derek\_Phillips](https://forum.inductiveautomation.com/u/Derek_Phillips)\
**Post date:** [June 23, 2023, 9:15pm UTC](https://forum.inductiveautomation.com/t/extracting-html-source-code-from-inline-frame/75481/1 "2023-06-23T21:15:52Z")

</div>

Hello All,

I currently have an inline frame directed to an internal site, that displays a web page with a couple of tables on it after the Session starts, and the IDP SSO completes its general Auth routine.

I figured there would be a property for the inline frame like: "Props.PageSource" so I can extract the HTML code from the inline browser. That does not seem to be the case, and I am looking for a solution to extract that data.

Any ideas on what I should try?

-Derek-

---

<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:** [June 23, 2023, 9:18pm UTC](https://forum.inductiveautomation.com/t/extracting-html-source-code-from-inline-frame/75481/2 "2023-06-23T21:18:04Z")

</div>

Web browsers don't allow you to do this cross-domain. If you want to 'scrape' a website, you need to authenticate to it and retrieve it programmatically using something like `system.net.httpClient`. The inline frame component is purely a convenience for the frontend.

---

<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:** [June 23, 2023, 9:25pm UTC](https://forum.inductiveautomation.com/t/extracting-html-source-code-from-inline-frame/75481/3 "2023-06-23T21:25:53Z")

</div>

> [@Derek\_Phillips](#):
>
> I figured there would be

It is natural for a programmer to think this way, but malware authors do too. This capability would enable a malicious website to offer an iframe to some other site as if it were that site, and gain access to everything the user does.

Don't even _ **wish** _ for this.

---

<div class="post-metadata">

**Author:** ![Derek\_Phillips](https://avatars.discourse-cdn.com/v4/letter/d/779978/32.png) [@Derek\_Phillips](https://forum.inductiveautomation.com/u/Derek_Phillips)\
**Post date:** [June 23, 2023, 9:37pm UTC](https://forum.inductiveautomation.com/t/extracting-html-source-code-from-inline-frame/75481/4 "2023-06-23T21:37:12Z")

</div>

Thank you both for the quick reply!

The reason I shied away from the system.net.httpClient, was I am having a rough time passing the session SSO credentials managed by the SAML IDP to gain access to the internal site. The inline frame was doing some automagic I don't quite understand yet. But I will study the httpClient calls further.

Have a good weekend.

-Derek-
