Skip to content

Bug: using FORWARDED_FOR_HEADER treats IP as IPv6 #19

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

Open
toredash opened this issue Oct 22, 2019 · 0 comments
Open

Bug: using FORWARDED_FOR_HEADER treats IP as IPv6 #19

toredash opened this issue Oct 22, 2019 · 0 comments

Comments

@toredash
Copy link
Contributor

toredash commented Oct 22, 2019

There seems to be a bug when using FORWARDED_FOR_HEADER.

I have scc-state behind a AWS ALB load balancer, which add "X-Forwarded-For" header to HTTP request to inform about the callers IP address. I added FORWARDED_FOR_HEADER="x-forwarded-for" to scc-state, and based on the logs from scc-state, it is reporting correctly the IP address of scc-worker and scc-broker processes connection to scc-state via the ALB.

But when scc-state calls getSCCBrokerClusterState, it will return an URI with brackets [] : https://github.com/SocketCluster/scc-state/blob/master/server.js#L79-L85, causing the workers to throw an parse error since ws://[10.150.34.147]:50020/socketcluster is not a valid URI.

It will only return a non-bracket (IPv4) URI if instanceIp is provided :

// Only set instanceIpFamily if data.instanceIp is provided.

I'm not sure if this is considered a bug, but I expected scc-state to be able to detect what instanceIpFamily should be when using FORWARDED_FOR_HEADER.

@toredash toredash changed the title Bug: using FORWARDED_FOR_HEADER threats IP as IPv6 Bug: using FORWARDED_FOR_HEADER treats IP as IPv6 Oct 22, 2019
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

No branches or pull requests

1 participant