NginxProxyManager / nginx-proxy-manager

Docker container for managing Nginx proxy hosts with a simple, powerful interface
https://nginxproxymanager.com
MIT License
22.27k stars 2.57k forks source link

Disable default headers set by nginx-proxy-manager #1785

Open SamuelNitsche opened 2 years ago

SamuelNitsche commented 2 years ago

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_pass directive is set in the configuration file.

Describe alternatives you've considered No alternatives I can think of.

vivedo commented 2 years ago

I faced the exact same issue and solved it by removing the proxy_set_header lines from the config template file and adding them in frontend/js/models/proxy-host-location.js as a default value for the advanced_config field, thus maintaining the default behaviour while allowing maximum configurability.

cb28f98

SamuelNitsche commented 2 years ago

Seems like a good solution. Could you make create a PR with these changes?

vivedo commented 2 years ago

Here it is #1844

jpdsc commented 1 year ago

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 1 year ago

+1

manuelmanhart commented 1 year ago

I have the same issue for some testing purposes, sadly the PR got deleted / closed :-(

github-actions[bot] commented 4 months ago

Issue is now considered stale. If you want to keep it open, please comment :+1:

peschee commented 1 month ago

This issue still persists… The configuration added in the advanced_config section is being added before the defaults.

See also https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2675#issuecomment-2298429185