Run interact server behing nginx proxy, real remote IP

[derekkddj]

If the Revheader is present, and the reverse proxy adds a header with the original IP (like X-Forwarded-For) you cna tun interact-sh server behing a proxy and get the real IP in the logs/client.

[derekkddj]

I dont know why it fails, because i have not touch the "interactsh-client" code, only in the server.

[Mzack9999]

@dhd0004 Thanks for opening this PR. This is for sure an interesting use-case scenario. If I'm not mistaken, the information related to the original IP would be contained within the dumped request as we capture the whole HTTP interaction. I guess the use case you are describing is to place a reverse proxy in front of an interactsh instance for internal testing?

[derekkddj]

@dhd0004 Thanks for opening this PR. This is for sure an interesting use-case scenario. If I'm not mistaken, the information related to the original IP would be contained within the dumped request as we capture the whole HTTP interaction. I guess the use case you are describing is to place a reverse proxy in front of an interactsh instance for internal testing?

Hi!

The scenario i am using is having only one server, with NGINX configured as Reverse Proxy. Behind the proxy i have the interactsh server, another apache web server, and one PHP application. If I acces for example web.mydomain.com, the nginx redirects the request to the internal web server. If i use interactsh.mydomain.com, the NGINX sends the request to the interactsh server.
The problem with this use case is that interactsh was showing always 127.0.0.1 as the remote address, because the nginx was between the real user and the interactsh server (is a rev proxy). So with this PR, my nginx sends the real remote IP addr to interactsh-server in an HTTP Header, and the interactsh server can show the real remote IP in the logs.

Regards