mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #98] URI support in proxy_pass #86
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#86
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jlesage on GitHub (Mar 7, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/98
The nginx
proxy_passdirective supports an URI:See http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_pass
It would be useful to support this. This could be especially useful for custom locations, where one would want to forward without the location part. For example, with:
The following forwarding would occur:
http://example.com/sub/index.html->http://192.168.1.1:8080/index.htmlOr with:
We would have:
http://example.com/sub/index.html->http://192.168.1.1:8080/other/index.html@jc21 commented on GitHub (Mar 7, 2019):
The former is already the case with Custom Locations released on 2.0.10. The latter could be an enhancement to that feature.
@jlesage commented on GitHub (Mar 7, 2019):
From what I see in genrated file, the
proxy_passis missing the ending slash, which makes nginx to not modify the forward URI.@kolbii commented on GitHub (Mar 10, 2019):
I just opened this PR #99 that resolves the sub-folder forwarding.
So it would look something like this:
location: /api
forward host: 1.1.1.1/custom-api
forward port: 8080
are proxied to 1.1.1.1:8080/custom-api
@briscula commented on GitHub (Nov 16, 2019):
Hi, Not sure where the problem is , but there is a bug in this feature.
{{ forward_path }}has same value as{{ path }}even if you provide a Forward Hostname without sub-folder. I just assume so, because I get a path not found from nginx when using it.@blade10101 commented on GitHub (Dec 25, 2023):
That responds with a blank page.