Improve custom locations, add disable feature #2429
Description
Hello, I have a feature request for a semi-standard use case and I am surprised it is not part of NPM yet, since it is, otherwise, a great software.
The standard use case for reverse proxy is proxying subdomains. However, because of DNS limitations, this is not possible for us. Therefore, we need to use path based proxying (e. g. localhost/gitlab).
Through custom locations, it is possible to add path-based entries to one proxied domain. What this means, however, is that disabling and organising single path-based entries is not possible.
Ideally, we would like to split custom locations into separate entries to disable them individually. Having just a "disable" switch for a custom location would be nice at a first glance. Maybe proxy entries with only path-based proxying could be selected when creating a new proxy entry and give such entries a custom UI.
Is your feature request related to a problem? Please describe.
Describe the solution you'd like
Implement a possibility or a sub-menu for proxied servers with only path-based entries. Make it possible to disable custom locations.
Describe alternatives you've considered
Not using NPM at all, because otherwise it only offers marginally more than not using it at all, sadly.
Additional context