Hi!
We ran into a similar thing a long time ago... I think the ELB Proxy
Protocol is the same as HAProxy's protocol which we were using (ELB did not
support the Proxy protocol back then). We solved this problem by
implementing a pre-parse event in node that let us pull data out of the
stream before handing it off to Node's http parser. I've put up a gist of
our preparse event handler [1] which pulls out the proxy protocol if it's
there, and it references the two commits to modify node to support this,
however that was on an earlier version of node and might take a little work
to get working (additionally, it requires maintaining a fork of node, which
is a pain). The product that used that code has since been shut down, so
we're not doing that anymore.
More recently on an unrelated project, I've hooked the on('connection')
event [2] to munge some data before sending it to node's http parser (since
it was crashing on some requests), and, though I didn't do it with piping,
it does seem to work, and I suspect a similar approach would work for
intercepting the Proxy protocol.
[1] https://gist.github.com/Jimbly/ec6126da15bf0e6f9a63
[2] https://gist.github.com/Jimbly/d996bd8c80ae1a376a0b#file-webroot-js-L141
Hope this helps!
Jimb Esser
On Tuesday, February 10, 2015 at 4:25:58 AM UTC-8, Fredrik Slättman wrote:
>
> Hi,
>
> first time poster, be gentle! :)
>
> I have a problem related to a WebSocket server behind AWS ELB, that's
> configured with TCP over SSL. The problem I'm experiencing is that I loose
> the origin IP of the connection, which I need for my application. So, to
> get the origin IP of the connection I need to enable Proxy Protocol Support
> for my ELB instance, which directly breaks the handshake for the WebSocket
> connections. I know that this issue can be solved by putting a nginx
> instance between the ELB and the WebSocket server, but I'm wondering if
> there is any other way? I would love to fix this with my current stack
> without adding another layer to it.
>
> The module I've found (node-proxywrap) seems to not be maintained anymore
> and consist one critical issue related to a memory leak, therefore that one
> is not an option.
>
> Anyone having any suggestions? I thought of piping the TCP connection in
> the http.on('connection' ...) event, but found quickly that the connection
> don't emit any events.
>
> Cheers,
> Fredrik Slättman
>
>
>
>
--
Job board: http://jobs.nodejs.org/
New group rules:
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
---
You received this message because you are subscribed to the Google Groups
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to nodejs+unsubscr...@googlegroups.com.
To post to this group, send email to nodejs@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/nodejs/9442d08f-9444-4538-ada4-fa38441f0c03%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
