Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pass some custom header. #208

Merged
merged 1 commit into from Oct 12, 2017
Merged

Pass some custom header. #208

merged 1 commit into from Oct 12, 2017

Conversation

trofim24
Copy link
Contributor

@trofim24 trofim24 commented Aug 4, 2016

Pass some custom header.

Pass some custom header.
@brycekahle
Copy link
Contributor

What proxy is setting those headers?

@trofim24
Copy link
Contributor Author

trofim24 commented Aug 5, 2016

What proxy is setting those headers?

These headers are used in conjunction with Amazon Elastic Load Balancing

@brycekahle
Copy link
Contributor

I do not see x-forwarded-host in that documentation. We already allow x-forwarded-for and x-forwarded-proto.

@trofim24
Copy link
Contributor Author

trofim24 commented Aug 9, 2016

Apache Module for x-forwarded-host
Amazon Elastic Load Balancing for x-forwarded-port

If you use a front-end service like Amazon, Apigee or other as the front-end to your APIs, you will need something like x-forwarded-host to understand what hostname was used to connect to the API, because Apigee gets configured with whatever your backend DNS is, nginx and your app stack only see the Host header as your backend DNS name, not the hostname that was called in the first place.
X-Forwarded-Port gives the port the client connected to on the proxy (e.g. 80 or 443)

@agolybev
Copy link

Hi @brycekahle, what about accept pull request?

@brycekahle brycekahle merged commit 50777ba into sockjs:master Oct 12, 2017
@trofim24 trofim24 deleted the patch-1 branch October 12, 2017 16:05
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.

None yet

3 participants