Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Conversation

jaggernoth
Copy link
Contributor

@jaggernoth jaggernoth commented May 23, 2018

Let's consider a scenario
proxy (Internet-facing) -> proxy(load balancer) -> application where both proxies will be based on node-http-proxy, with current logic original host to be lost
With updated logic the original forwarded host will be passed down the proxy chain

With more than 1 proxy the original host was lost, now it will be passed down the proxy chain
Copy link
Contributor

@jcrugzz jcrugzz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@jcrugzz
Copy link
Contributor

jcrugzz commented Jun 6, 2018

@jaggernoth host is probably most important but should we also default the other values so we are consistent?

@jaggernoth
Copy link
Contributor Author

jaggernoth commented Jun 11, 2018

@jcrugzz : From what I can see in the code for other x-forwarded header entries new levels are concatenated as CSV values and I was considering making x-forwarded-host a CSV value as well but it would be much riskier as it may cause compatibility issues (CSV requires additional parsing).
AFAIK there is no real consensus on how the mechanism should work, but bare in mind I've done very minimal research just to make my code work;).
One thing is certain: just overwriting the host seems to defeat the purpose of this header.

Copy link
Member

@indexzero indexzero left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree with @jcrugzz comment, but this PR is still 👍

As to the CSV value question @jaggernoth the research I briefly looked at did not suggest that as a format:

@indexzero indexzero merged commit 36bfe56 into http-party:master Aug 22, 2019
mcheshkov pushed a commit to gemini-testing/node-http-proxy that referenced this pull request Sep 16, 2019
With more than 1 proxy the original host was lost, now it will be passed down the proxy chain
This was referenced Mar 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.