# Prodigy behind reverse proxy

**URL:** <https://support.prodi.gy/t/prodigy-behind-reverse-proxy/1993>\
**Category:** Uncategorized\
**Tags:** usage, install\
**Created:** [September 9, 2019, 1:43pm UTC](https://support.prodi.gy/t/prodigy-behind-reverse-proxy/1993 "2019-09-09T13:43:25Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![honnibal](https://sea2.discourse-cdn.com/flex020/user_avatar/support.prodi.gy/honnibal/32/35_2.png) [@honnibal](https://support.prodi.gy/u/honnibal)\
**Post date:** [September 9, 2019, 2:20pm UTC](https://support.prodi.gy/t/prodigy-behind-reverse-proxy/1993/2 "2019-09-09T14:20:21Z")

</div>

Unfortunately we don't support path-based routing. 😢 I wanted this too for our own deployments and really tried to get it to work, but as far as I can see there's no good way to do it that doesn't require recompiling the front-end once the desired subpath is known.

The solution is to use subdomain routing instead. So instead of `/instance_one/get_questions` you'll have `instance_one.example.com/get_questions`. See further discussion here: [Feature request: URL prefixing](https://support.prodi.gy/t/feature-request-url-prefixing/1898/2)

---

_[View the full topic](https://support.prodi.gy/t/prodigy-behind-reverse-proxy/1993)._