# Embedding Session in a Webpage

**URL:** <https://forum.inductiveautomation.com/t/embedding-session-in-a-webpage/50200>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [August 23, 2021, 8:39pm UTC](https://forum.inductiveautomation.com/t/embedding-session-in-a-webpage/50200 "2021-08-23T20:39:58Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![jspecht](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jspecht/32/6465_2.png) [@jspecht](https://forum.inductiveautomation.com/u/jspecht)\
**Post date:** [August 26, 2021, 11:25pm UTC](https://forum.inductiveautomation.com/t/embedding-session-in-a-webpage/50200/14 "2021-08-26T23:25:55Z")

</div>

Actually, adding the reverse proxy can cause issues if you do SSL termination at the proxy and connect proxy → ignition gateway with insecure http. In that case, the Gateway will consider the connection as insecure, and will _not_ set the `Secure` attribute on the session cookie, which browsers require for pages embedded in a cross-origin context. So…when you _do_ add a RP in front of the Gateway, you will need to do one of the following:

1. Do not perform SSL termination at the proxy (proxy forwards TLS traffic through to the Gateway)
2. If you do perform SSL termination at the proxy, then make sure the proxy connects to Ignition over secure https
3. If you are on 8.1.10, you could opt-into [the new “Use Proxy Forwarded Headers” setting in Config \> Networking \> Webserver](https://forum.inductiveautomation.com/t/nightly-8-1-changelogs-2021/42410/128) and then configure the proxy to send the appropriate `Forwarded` and/or `X-Forwarded-*` suite of headers so that Ignition will treat the connection as secure even if the connection between the proxy and Gateway is insecure.

---

_[View the full topic](https://forum.inductiveautomation.com/t/embedding-session-in-a-webpage/50200)._