# URL forwarding or limiting (:8088/data/perspective/client/)

**URL:** <https://forum.inductiveautomation.com/t/url-forwarding-or-limiting-8088-data-perspective-client/95196>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [August 27, 2024, 10:45am UTC](https://forum.inductiveautomation.com/t/url-forwarding-or-limiting-8088-data-perspective-client/95196 "2024-08-27T10:45:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Theodorska](https://avatars.discourse-cdn.com/v4/letter/t/34f0e0/32.png) [@Theodorska](https://forum.inductiveautomation.com/u/Theodorska)\
**Post date:** [August 27, 2024, 10:45am UTC](https://forum.inductiveautomation.com/t/url-forwarding-or-limiting-8088-data-perspective-client/95196/1 "2024-08-27T10:45:30Z")

</div>

Hello,

We have used a single ignition gateway to make multiple projects. One of the projects is available for thirdparty endusers. We want to use a simple URL to access the project, because right now they must use our custom url + ":8088/data/perspective/client/XXXXX".

We not yet figured out a way to mask the URL or redirect to avoid that the thirdparty endusers can remove "/data/perspective/client/XXXXX" from the URL and access the login page for our main gateway.

Any suggestions? I read an earlier post saying that this was potentially not possible

---

<div class="post-metadata">

**Author:** ![Benjamin\_Furlani](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/benjamin_furlani/32/66084_2.png) [@Benjamin\_Furlani](https://forum.inductiveautomation.com/u/Benjamin_Furlani)\
**Post date:** [August 27, 2024, 11:10am UTC](https://forum.inductiveautomation.com/t/url-forwarding-or-limiting-8088-data-perspective-client/95196/2 "2024-08-27T11:10:17Z")

</div>

You could utilize nginx and setup proxy for that url to be `www.somedomain.com/applicationEndpoint` inside of the `.conf`

Here is some documentation on nginx. [NGINX Reverse Proxy | NGINX Documentation](https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/)

---

<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:** [August 27, 2024, 11:34am UTC](https://forum.inductiveautomation.com/t/url-forwarding-or-limiting-8088-data-perspective-client/95196/3 "2024-08-27T11:34:58Z")

</div>

> [@Theodorska](#):
>
> custom url + ":8088

I hope this is only inside a VPN. If you've exposed Ignition on a public address without SSL, your gateway is wide open for attack, and all user logins are crossing the public network in **clear text**. This is extremely dangerous to your gateway and to your clients.

---

<div class="post-metadata">

**Author:** ![Theodorska](https://avatars.discourse-cdn.com/v4/letter/t/34f0e0/32.png) [@Theodorska](https://forum.inductiveautomation.com/u/Theodorska)\
**Post date:** [August 27, 2024, 11:46am UTC](https://forum.inductiveautomation.com/t/url-forwarding-or-limiting-8088-data-perspective-client/95196/4 "2024-08-27T11:46:53Z")

</div>

We do have our endusers accessing our site with SSL using the other port. I just did not remember the port while writing the post, hehe!

---

<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:** [August 27, 2024, 11:51am UTC](https://forum.inductiveautomation.com/t/url-forwarding-or-limiting-8088-data-perspective-client/95196/5 "2024-08-27T11:51:49Z")

</div>

> [@Theodorska](#):
>
> mask the URL

You won't be able to do this. Even behind a proxy, Ignition expects its URLs to have that format, and will generate such URLs all over the place.

> [@Theodorska](#):
>
> access the login page for our main gateway.

This **can** be filtered out by a proxy in front of Ignition. But you must be specific on what to filter--Perspective clients need resources from the gateway that are not all under `/data/perspective/....`