Allow customising ProxyAddHeaders #952
Comments
nbarrientos
added a commit
to nbarrientos/puppet-foreman
that referenced
this issue
May 12, 2021
When the Apache instance configured by this module is not dealing with user requests directly because there's another proxy in front, it's undesirable that the "local" Apache resets headers like X-Forwarded-Host. When it does, it could happen that links created using Rails _url helpers do not contain the Host initially sent by the client leading to broken links (as they point to backend nodes not reachable by the user). This patch makes this setting customisable by the administrator by exposing it a parameter. Fixes theforeman#952
nbarrientos
added a commit
to nbarrientos/puppet-foreman
that referenced
this issue
May 12, 2021
When the Apache instance configured by this module is not dealing with user requests directly because there's another proxy in front, it's undesirable that the "local" Apache resets headers like X-Forwarded-Host. When it does, it could happen that links created using Rails _url helpers do not contain the Host initially sent by the client leading to broken links (as they point to backend nodes not reachable by the user). This patch makes this setting customisable by the administrator by exposing it a parameter. Fixes theforeman#952
ekohl
pushed a commit
that referenced
this issue
May 12, 2021
When the Apache instance configured by this module is not dealing with user requests directly because there's another proxy in front, it's undesirable that the "local" Apache resets headers like X-Forwarded-Host. When it does, it could happen that links created using Rails _url helpers do not contain the Host initially sent by the client leading to broken links (as they point to backend nodes not reachable by the user). This patch makes this setting customisable by the administrator by exposing it a parameter. Fixes #952
cegeka-jenkins
pushed a commit
to cegeka/puppet-foreman
that referenced
this issue
Feb 3, 2022
When the Apache instance configured by this module is not dealing with user requests directly because there's another proxy in front, it's undesirable that the "local" Apache resets headers like X-Forwarded-Host. When it does, it could happen that links created using Rails _url helpers do not contain the Host initially sent by the client leading to broken links (as they point to backend nodes not reachable by the user). This patch makes this setting customisable by the administrator by exposing it a parameter. Fixes theforeman#952
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When the Apache instance configured by this module is not dealing with user requests directly because there's another proxy in front, it's undesirable that the "local" Apache resets headers like
X-Forwarded-Host. When it does, it could happen that links created using Rails_urlhelpers do not contain theHostinitially sent by the client leading to broken links (as they point to backend nodes not reachable by the user).The task is to make this configurable by adding a parameter to
foreman::config::apache.The text was updated successfully, but these errors were encountered: