# Re-Direct URL's - Perspective

**URL:** <https://forum.inductiveautomation.com/t/re-direct-urls-perspective/29361>\
**Category:** Ignition\
**Created:** [October 24, 2019, 5:07pm UTC](https://forum.inductiveautomation.com/t/re-direct-urls-perspective/29361 "2019-10-24T17:07:14Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![hodgins.e](https://avatars.discourse-cdn.com/v4/letter/h/977dab/32.png) [@hodgins.e](https://forum.inductiveautomation.com/u/hodgins.e)\
**Post date:** [October 24, 2019, 5:07pm UTC](https://forum.inductiveautomation.com/t/re-direct-urls-perspective/29361/1 "2019-10-24T17:07:14Z")

</div>

Is it possible to re-direct URLS? We have https sites for Ignition running on port 8443 and it would be nice to have a cleaner URL for our users. For example:

> https://{DOMAIN}/data/perspective/client/{PROJECT\_NAME}

gets redirected to port 8443:

> https://{DOMAIN}:8443/data/perspective/client/{PROJECT\_NAME}

So, any url that has **/data/perspective/client** gets redirected to port 8443 with the appropriate project name.

---

<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:** [October 24, 2019, 5:14pm UTC](https://forum.inductiveautomation.com/t/re-direct-urls-perspective/29361/2 "2019-10-24T17:14:22Z")

</div>

Sure, it’s possible - but you’ll need another webserver running in port 443 to act as a reverse proxy; look into something like `nginx` if running on a Linux system. `https://` with no specific port just tells browsers/etc to use port 443, so you’ll still need _something_ listening there that’s able to do the redirection.

---

<div class="post-metadata">

**Author:** ![hodgins.e](https://avatars.discourse-cdn.com/v4/letter/h/977dab/32.png) [@hodgins.e](https://forum.inductiveautomation.com/u/hodgins.e)\
**Post date:** [October 24, 2019, 5:18pm UTC](https://forum.inductiveautomation.com/t/re-direct-urls-perspective/29361/3 "2019-10-24T17:18:40Z")

</div>

ok, thanks! we’re running Apache. I just wasn’t sure if we set it to listen to port 8443 it would still work with Ignition’s webserver.

---

<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:** [October 24, 2019, 5:21pm UTC](https://forum.inductiveautomation.com/t/re-direct-urls-perspective/29361/4 "2019-10-24T17:21:59Z")

</div>

Well, you can’t have two services bound to the _same_ port - so if you want `https://domain` to be what users are using, then I would have Apache bound to **443** , reverse-proxying Ignition running on **8443**. That also has the security benefit of not requiring Ignition to run as root to bind to a system-level port.

---

<div class="post-metadata">

**Author:** ![hodgins.e](https://avatars.discourse-cdn.com/v4/letter/h/977dab/32.png) [@hodgins.e](https://forum.inductiveautomation.com/u/hodgins.e)\
**Post date:** [October 24, 2019, 5:27pm UTC](https://forum.inductiveautomation.com/t/re-direct-urls-perspective/29361/5 "2019-10-24T17:27:36Z")

</div>

that makes sense, thank you! I’ll have to do some googling on how reverse proxy apache though as I’ve never had to do that before.