mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-28 10:55:54 +03:00
[GH-ISSUE #1318] Allow "return defined HTTP code without redirection" for custom location on redirect host #1052
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#1052
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 @Apollon77 on GitHub (Aug 14, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1318
Is your feature request related to a problem? Please describe.
I have an application that is forwarded by npm and that works great. Now I had the case where one "user" (identified by an own "id" in the application path) spammed the application. So I checked out if I can prevent that being forwarded to the real application by using custom location sessings ... but I learned that I could "only" forward a certain part to a host ...
Describe the solution you'd like
It would be great if "providing a redirect location" for a custom location is only one option. The second could be maybe to have it as a "return http code xyz" and so also allow "redirect host" functionality or maybe 404-host-functionality on a custom location
Describe alternatives you've considered
next I wated to check if I can do that maself by providing a custom nginx config for that case. Need to look into that next days.
@github-actions[bot] commented on GitHub (Mar 6, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@Apollon77 commented on GitHub (Mar 6, 2024):
would be still an interesting feature
@github-actions[bot] commented on GitHub (Dec 8, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (Dec 31, 2025):
Issue was closed due to inactivity.