mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-28 10:55:54 +03:00
[GH-ISSUE #1785] Disable default headers set by nginx-proxy-manager #1318
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#1318
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 @SamuelNitsche on GitHub (Jan 21, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1785
Is your feature request related to a problem? Please describe.
I have a case where the proxied application stops working if the default Host header (
proxy_set_header Host $host) is set. This is done automatically by nginx-proxy-manager.Describe the solution you'd like
Add a checkbox (unchecked by default) to create a "raw" proxy where only the
proxy_passdirective is set in the configuration file.Describe alternatives you've considered
No alternatives I can think of.
@vivedo commented on GitHub (Feb 10, 2022):
I faced the exact same issue and solved it by removing the
proxy_set_headerlines from the config template file and adding them infrontend/js/models/proxy-host-location.jsas a default value for theadvanced_configfield, thus maintaining the default behaviour while allowing maximum configurability.cb28f98
@SamuelNitsche commented on GitHub (Feb 10, 2022):
Seems like a good solution. Could you make create a PR with these changes?
@vivedo commented on GitHub (Feb 10, 2022):
Here it is #1844
@jpdsc commented on GitHub (Dec 12, 2022):
I'm facing the same issue when adding Authelia in the custom locations instead of advanced tab.
Due to 1 or more proxy_set_header which is added as default causes the login to not work.
Is there news on when this PR will be released?
@CrazyFluffyPony commented on GitHub (Dec 18, 2022):
+1
@manuelmanhart commented on GitHub (Aug 29, 2023):
I have the same issue for some testing purposes, sadly the PR got deleted / closed :-(
@github-actions[bot] commented on GitHub (May 5, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@peschee commented on GitHub (Aug 28, 2024):
This issue still persists… The configuration added in the
advanced_configsection is being added before the defaults.See also https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2675#issuecomment-2298429185
@rafael-manochio commented on GitHub (Jan 31, 2025):
Can confirm, this issue still exists in version v2.12.2.
Someone found a workaround?
@KevinMitchell commented on GitHub (Apr 24, 2025):
Am I correct in thinking that at present if I have any service that requires the Host header to be set to anything other than $host then I can't use Nginx proxy manager and must use "raw" Nginx? What was the logic behind loading additional headers BEFORE the predefined ones? It seems bizarre so I'm curious what the reasoning was.
@github-actions[bot] commented on GitHub (Nov 8, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍