How do I get user IP address in django

Question

How do I get user s IP in django   I have a view like this     Create your views from django contrib gis utils import GeoIP from django template import  RequestContext from django shortcuts import render to response   def home request     g   GeoIP     client ip   request META  REMOTE ADDR     lat long   g lat lon client ip    return render to response  home page tmp html  locals      But I get this error   KeyError at  mypage       REMOTE ADDR      Request Method  GET     Request URL     http   mywebsite com mypage      Django Version  1 2 4     Exception Type  KeyError     Exception Value           REMOTE ADDR      Exception Location   mysite homepage views py in home  line 9     Python Executable    usr bin python     Python Version  2 6 6     Python Path        mysite     usr local lib python2 6 dist-packages flup-1 0 2-py2 6 egg     usr lib python2 6     usr lib python2 6 plat-linux2     usr lib python2 6 lib-tk     usr lib python2 6 lib-old     usr lib python2 6 lib-dynload     usr local lib python2 6 dist-packages     usr lib python2 6 dist-packages     usr lib pymodules python2 6       Server time     Sun  2 Jan 2011 20 42 50 -0600

User · Answer

here is a short one liner to accomplish this   request META get  HTTP X FORWARDED FOR   request META get  REMOTE ADDR        split      0  strip

User · Answer

I was also missing proxy in above answer  I used get ip address from request from django easy timezones     from easy timezones utils import get ip address from request  is valid ip  is local ip ip   get ip address from request request  try      if is valid ip ip           geoip record   IpRange objects by ip ip  except IpRange DoesNotExist      return None   And here is method get ip address from request  IPv4 and IPv6 ready     def get ip address from request request           Makes the best attempt to get the client s real IP or return the loopback         PRIVATE IPS PREFIX     10     172     192     127        ip address          x forwarded for   request META get  HTTP X FORWARDED FOR           if x forwarded for and     not in x forwarded for          if not x forwarded for startswith PRIVATE IPS PREFIX  and is valid ip x forwarded for               ip address   x forwarded for strip       else          ips    ip strip   for ip in x forwarded for split               for ip in ips              if ip startswith PRIVATE IPS PREFIX                   continue             elif not is valid ip ip                   continue             else                  ip address   ip                 break     if not ip address          x real ip   request META get  HTTP X REAL IP               if x real ip              if not x real ip startswith PRIVATE IPS PREFIX  and is valid ip x real ip                   ip address   x real ip strip       if not ip address          remote addr   request META get  REMOTE ADDR               if remote addr              if not remote addr startswith PRIVATE IPS PREFIX  and is valid ip remote addr                   ip address   remote addr strip       if not ip address          ip address    127 0 0 1      return ip address

User · Answer

The reason the functionality was removed from Django originally was that the header cannot ultimately be trusted  The reason is that it is easy to spoof  For example the recommended way to configure an nginx reverse proxy is to   add header X-Forwarded-For  proxy add x forwarded for  add header X-Real-Ip        remote addr    When you do   curl -H  X-Forwarded-For  8 8 8 8  192 168 1 2  http   192 168 1 3    Your nginx in myhost com will send onwards   X-Forwarded-For  8 8 8 8  192 168 1 2  192 168 1 3   The X-Real-IP will be the IP of the first previous proxy if you follow the instructions blindly   In case trusting who your users are is an issue  you could try something like django-xff  https   pypi python org pypi django-xff

User · Answer

def get client ip request       x forwarded for   request META get  HTTP X FORWARDED FOR       if x forwarded for          ip   x forwarded for split      0      else          ip   request META get  REMOTE ADDR       return ip   Make sure you have reverse proxy  if any  configured correctly  e g  mod rpaf installed for Apache    Note  the above uses the first item in X-Forwarded-For  but you might want to use the last item  e g   in the case of Heroku  Get client  39 s real IP address on Heroku   And then just pass the request as argument to it   get client ip request

User · Answer

In django VERSION  2  1  1   final   0  request handler  sock request  stream stream raw  sock   lt socket socket fd 1236  family AddressFamily AF INET  type SocketKind SOCK STREAM  proto 0  laddr   192 168 1 111   8000   raddr   192 168 1 111   64725  gt  client ip port sock getpeername     if you call above code twice you may got  AttributeError    io BytesIO  object has no attribute  stream      AttributeError   LimitedStream  object has no attribute  raw

User · Answer

You can use django-ipware which supports Python 2  amp  3 and handles IPv4  amp  IPv6   Install    pip install django-ipware  Simple Usage     In a view or a middleware where the  request  object is available  from ipware import get client ip ip  is routable   get client ip request  if ip is None        Unable to get the client s IP address else        We got the client s IP address     if is routable            The client s IP address is publicly routable on the Internet     else            The client s IP address is private    Order of precedence is  Public  Private  Loopback  None    Advanced Usage    Custom Header - Custom request header for ipware to look at   i  r   get client ip request  request header order   X FORWARDED FOR    i  r   get client ip request  request header order   X FORWARDED FOR    REMOTE ADDR     Proxy Count - Django server is behind a fixed number of proxies   i  r   get client ip request  proxy count 1   Trusted Proxies - Django server is behind one or more known  amp  trusted proxies   i  r   get client ip request  proxy trusted ips   177 2 2 2       For multiple proxies  simply add them to the list i  r   get client ip request  proxy trusted ips   177 2 2 2    177 3 3 3       For proxies with fixed sub-domain and dynamic IP addresses  use partial pattern i  r   get client ip request  proxy trusted ips   177 2     177 3        Note  read this notice

User · Answer

Alexander s answer is great  but lacks the handling of proxies that sometimes return multiple IP s in the HTTP X FORWARDED FOR header   The real IP is usually at the end of the list  as explained here  http   en wikipedia org wiki X-Forwarded-For  The solution is a simple modification of Alexander s code   def get client ip request       x forwarded for   request META get  HTTP X FORWARDED FOR       if x forwarded for          ip   x forwarded for split      -1  strip       else          ip   request META get  REMOTE ADDR       return ip

User · Answer

The simpliest solution  in case you are using fastcgi nignx  is what itgorilla commented       Thank you for this great question  My fastcgi was not passing the REMOTE ADDR meta key  I added the line below in the nginx conf and fixed the problem  fastcgi param REMOTE ADDR  remote addr      itgorilla   Ps  I added this answer just to make his solution more visible

User · Answer

I would like to suggest an improvement to yanchenko s answer   Instead of taking the first ip in the X FORWARDED FOR list  I take the first one which in not a known internal ip  as some routers don t respect the protocol  and you can see internal ips as the first value of the list   PRIVATE IPS PREFIX     10     172     192       def get client ip request          get the client ip from the request             remote address   request META get  REMOTE ADDR         set the default value of the ip to be the REMOTE ADDR if available       else None     ip   remote address       try to get the first non-proxy ip  not a private ip  from the       HTTP X FORWARDED FOR     x forwarded for   request META get  HTTP X FORWARDED FOR       if x forwarded for          proxies   x forwarded for split                remove the private ips from the beginning         while  len proxies   gt  0 and                 proxies 0  startswith PRIVATE IPS PREFIX                proxies pop 0            take the first ip which is not a private one  of a proxy          if len proxies   gt  0              ip   proxies 0       return ip   I hope this helps fellow Googlers who have the same problem

User · Answer

No More confusion In the recent versions of Django it is mentioned clearly that the Ip address of the client is available at   request META get  REMOTE ADDR     for more info check the Django Docs

User · Answer

In my case none of above works  so I have to check uwsgi   django source code and pass static param in nginx and see why how  and below is what I have found   Env info  python version  2 7 5 Django version   1  6  6   final   0  nginx version  nginx 1 6 0 uwsgi  2 0 7    Env setting info  nginx as reverse proxy listening at port 80 uwsgi as upstream unix socket  will response to the request eventually  Django config info   USE X FORWARDED HOST   True   with or without this line does not matter   nginx config   uwsgi param      X-Real-IP               remote addr     uwsgi param   X-Forwarded-For         proxy add x forwarded for     uwsgi param   HTTP X FORWARDED FOR    proxy add x forwarded for      hardcode for testing uwsgi param      X-Forwarded-For         10 10 10 10   uwsgi param      HTTP X FORWARDED FOR    20 20 20 20     getting all the params in django app   X-Forwarded-For         10 10 10 10 HTTP X FORWARDED FOR    20 20 20 20   Conclusion    So basically  you have to specify exactly the same field param name in nginx  and use request META field param  in django app   And now you can decide whether to add a middleware  interceptor  or just parse HTTP X FORWARDED FOR in certain views

[python] How do I get user IP address in django?

Examples related to python

Examples related to django