Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

feature request- capture ip address onto response object

See original GitHub issue

this is an extension of a request from the requests library (https://github.com/kennethreitz/requests/issues/2158)

I recently ran into an issue with the various “workarounds”, and have been unable to consistently access an open socket across platforms, environments, or even servers queried (the latter might be from unpredictable timeouts)

it would honestly be great if the remote ip address were cached onto the response object by this library.

Issue Analytics

State:
Created 7 years ago
Reactions:5
Comments:43 (20 by maintainers)

Top GitHub Comments

8reactions

misotrnkacommented, Jan 18, 2020

I would also like to +1 on this request. Knowing the IP address is essential for many use-cases. For example, rate-limiting requests per IP address. I don’t think any of the proposed work-arounds really work consitently.

2reactions

jvanascocommented, Jun 9, 2020

After quite some time experimenting with different methods, I’ve found a workaround that works consistently:

Elaborating off what @sigmavirus24 said - it’s not a workaround. You are creating a second request and obtaining DNS info from that. You may consistently get an ip address off that method, but there is no guarantee the ip address was associated with the first request. When dealing with domains that are fronted by CDNs or Load Balancers, there is a decreased chance the information will match up.