Make use of HTTP Proxy more flexible

[b1167684@…]

For security reasons I like to have a web server/proxy in front of my applications (like FreeNAS). This proxy is used for several applications on the same TCP Port. The applications were distinguished by a context part of the URL:

--- SNIP httpd.conf ---

ProxyPass        /openqrm/ https://openqrm.int.example.com/openqrm/
ProxyPassReverse /openqrm/ https://openqrm.int.example.com/openqrm/

ProxyPass        /zabbix/ https://zabbix.int.example.com/zabbix/
ProxyPassReverse /zabbix/ https://zabbix.int.example.com/zabbix/

ProxyPass        /freenas/ https://freenas.int.example.com/freenas/
ProxyPassReverse /freenas/ https://freenas.int.example.com/freenas/

--- SNAP httpd.conf ---

That doesn't work because the FreeNAS UI expects any request on the root of the URL. Using a configuration like this:

--- SNIP httpd.conf ---

ProxyPass        /freenas/ https://freenas.int.example.com/
ProxyPassReverse /freenas/ https://freenas.int.example.com/

--- SNAP httpd.conf ---

doesn't work either, because the URL gets rewritten by the FreeNAS UI without the context part which then will not be forwarded by the proxy.

It would be nice to change the expected URL context of the FreeNAS UI web server or also allow access by an additional (maybe configurable) context like '/freenas/'

[william]

This is how django operates, changing this behavior is very counter-productive and honestly there are bigger problems to take care of.

If anyone is willing to provide a patch, it will be happily reviewed.