# Feasible to reverse proxy using qualifier in URL?

**URL:** <https://meta.discourse.org/t/feasible-to-reverse-proxy-using-qualifier-in-url/33623>\
**Category:** Product Support\
**Created:** [23 Settembre 2015, 12:39am UTC](https://meta.discourse.org/t/feasible-to-reverse-proxy-using-qualifier-in-url/33623 "2015-09-23T00:39:27Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![ckamps](https://avatars.discourse-cdn.com/v4/letter/c/e95f7d/32.png) [@ckamps](https://meta.discourse.org/u/ckamps)\
**Post date:** [23 Settembre 2015, 12:39am UTC](https://meta.discourse.org/t/feasible-to-reverse-proxy-using-qualifier-in-url/33623/1 "2015-09-23T00:39:27Z")

</div>

I’ve seen many references to configuring reverse proxies to map “/” to a backend Discourse site, but I haven’t seen examples where something other than slash is mapped. For example, I would like to establish a reverse proxy to map multiple Discourse sites by qualifying the URL after the host/domain name.

```
ProxyPreserveHost On
ProxyRequests Off
ProxyPass /meta/ http://<IP address 1>/
ProxyPassReverse /meta/ http://<IP address 1>/
ProxyPass /foo/ http://<IP address 2>/
ProxyPassReverse /foo/ http://<IP address 2>/

```

When this approach is taken, the main page is loaded, but all references back to the site lack the “/meta/” qualifier and result in 404s.

Is it feasible to prefix Discourse sites addresses in this manner?

I’d prefer not to use different FQDNs to distinguish between sites.

---

_[View the full topic](https://meta.discourse.org/t/feasible-to-reverse-proxy-using-qualifier-in-url/33623)._