Russell,
I agree with the spoofing comment you made and it makes sense not to
provide a formal API.
I wish there was a middle-ground here, however, at this time, I do not have
a solid reason to make a case here. (not yet at least :)
BTW: IP logic was updated as per your feedback.
Thank you.
On Mon, Dec 23, 2013 at 7:27 AM, Val Neekman wrote:
> Majority of the sites/apps built on Django *may* require user's real IP
> address for tracking, prevention, verification and many other reasons.
>
> To get (guess) user's real IP address, one must check few META fields in a
*correction*:
It should read: "*may I propose*" instead of "may I purpose".
Thanks,
Val
On Sun, Dec 22, 2013 at 6:27 PM, Val Neekman wrote:
> Majority of the sites/apps built on Django *may* require user's real IP
> address for tracking, prevention, verification and many
Majority of the sites/apps built on Django *may* require user's real IP
address for tracking, prevention, verification and many other reasons.
To get (guess) user's real IP address, one must check few META fields in a
particular order to peel off the proxies.
This is what lot of Django