search

httptoolkit / httptoolkit

HTTP Toolkit is a beautiful & open-source tool for debugging, testing and building with HTTP(S) on Windows, Linux & Mac :tada: Open an issue here to give feedback or ask for help.
https://httptoolkit.com
2.77k stars 71 forks source link

Expose IP address data from intercepted traffic #416

Open pimterry opened 1 year ago

pimterry commented 1 year ago

In some cases it can be useful to be able to directly access the client's remote address (IP and port) for received traffic.

It might also be useful to view the resolved upstream/destination IP address, where there is one (for forwarded traffic).

If you're interested in this and you have a specific motivating use case, please share it here to add context.

Does this affect you too? Click below and add a :+1: to vote for this and help decide where HTTP Toolkit goes next, or go vote on the other most popular ideas so far.

nutterthanos commented 1 year ago

so for example there is an website that is protected by cloudflare, would the upstream ip as such be the actual ip of the website and not an cloudflare ip if there is such an ip that can be resolved?

pimterry commented 1 year ago

No - if the server that HTTP Toolkit talks to is a reverse proxy/CDN/etc, then it's not possible to know the address of the servers behind it providing the data further upstream. They might not even have a publicly routeable address at all.

It's only possible to report the resolved public IP addresses & ports of the client that connects to HTTP Toolkit and the server that HTTP Toolkit directly connects to, not what might be going on beyond that.