Read IP and port from headers

[everissimo]

When I execute the server behind a reverse proxy, I get 127.0.0.1 as ip. I configured the headers to write X-Real-IP, but there is no way to access it. What should be the right way to get the user ip?

[vti]

Normally I would use a wrapper around Protocol::WebSocket, like a PSGI application or so, so you can get IP before going to Protocol::WebSocket if you need it.

You can probably use a hack for accessing $req->{headers} structure if you're brave enough.. :)

[everissimo]

The problem is I am using another module, Net::WebSocket::Server, that uses Protocol::WebSocket. The best way to get this information is to change Protocol::WebSocket and expose the headers, as you suggested. I'm going to do that, so I can have my system working. Would it be a good patch for Protocol::WebSocket? Or would there be any reason for not adding this feature? Thank you! Em seg., 2 de dez. de 2019 às 06:13, Viacheslav Tykhanovskyi < notifications@github.com> escreveu:

…

Normally I would use a wrapper around Protocol::WebSocket, like a PSGI application or so, so you can get IP before going to Protocol::WebSocket if you need it. You can probably use a hack for accessing $req->{headers} structure if you're brave enough.. :) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#64?email_source=notifications&email_token=AAHZB7HWLMLSTRBFBEXISNTQWTGSRA5CNFSM4JTIOP6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFSY6ZI#issuecomment-560303973>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAHZB7HQHQ5QXPIDSXR63G3QWTGSRANCNFSM4JTIOP6A> .