Using django-ipware get_client_ip instead of get_real_ip about django-ipware

[un33k]

@shadinaif Version 1 was simple and just wanted to get your the first routable IP address it found so users could identify clients uniquely.

Version 2 on the other hand, allows the advanced users to pass in the trusted proxies, the number of proxies as well as a custom right-most flag, as per their network configuration.

The default behavior is to find the left-most ip address for HTTP_X_FORWARDED_FOR OR X_FORWARDED_FOR and if that IP is not routable, it will go down the IPWARE_META_PRECEDENCE_ORDER to find the best routable IP address.

As for HTTP_X_FORWARDED_FOR OR X_FORWARDED_FOR, if the left most IP address is not routable, it cannot be client's read IP address, so it skips over to find the next routable IP.

SemVer was update to 2.0 indicating a backward incompatibility.

Feel free to switch to version two.

Closing the issue, but feel free to reopen if you feel that you have found a bug in version 2.

[shadinaif]

Thank you @un33k 👍

[kleptog]

The above explanation is a bit incomplete. If I read the code right, it stops on the first public IP, so if you are coming from a local private network, then get_client_ip will return based on the lowest priority header. Not necessarily a problem, but not an obvious change from the previous version.

Just had to fix our test cases :)

[un33k]

@kleptog Moving from 1.x to 2.x was a breaking change and the behavior changed as well. Therefore your test cases that were for 1.x needed to also changed. Hope this helps,

[un33k]

@kleptog django-ipware is on its way to being deprecated.

With that said, I have a python package that is going to replace it.

Have a look at python-ipware and if works for you switch to it.

Feedback is welcomed.