Many times you many need the IP address of the computer that's accessing your webapp. You may want it for a survey, or cataloging that user to offer better services and what not. Today we'll see not only how to get the IP address, but a host of other client side information that can be used to fine tune your app.
Let's take the IP address for example. I once needed it to see from where the app was being accessed from the most. I wrote a tracker that would piggyback on the client's signal and work backwards all the way to the source and get me the IP address. But little did I know that Django already does that for me. The IP address and host name (ISP) is encoded in the request parameter. Let's see how to view them.
To do this we'll create a simple view. In HTML, we'll create a list that contains header name and value, and then populate it through Django.
headers.html
<html>
<head><title>Django HTTP headers</title></head>
<body>
<ul>
{% for header in headers %}
<li><b>{{ header.name }}</b>: {{ header.value }}</li>
{% endfor %}
</ul>
</body>
</html>
Pretty straightforward. Now let's populate the list.
views.py
from django.shortcuts import render
class Header (object):
def __init__ (self, name, value):
self.name, self.value = name, value
def headers (request):
headers = []
headers_list = request.META.items ()
for name, value in headers_list:
headers.append (Header (name, value))
return render (request, "headers.html", {"headers":headers})
Let's see what's going on here. First, we import the render function. Then, we create a class called Header for use in the templating language. We already saw this with Student in Django Templating Language - Part IV. Now, request.META contains a list of headers and its method items() returns a list of tuples with name and value. We use that to populate the list in HTML.
One more thing. Notice how I provided the context directly as a parameter in the render function call? You can do that too. There's no need to do the Template/Context schedule each time.
Let's take the IP address for example. I once needed it to see from where the app was being accessed from the most. I wrote a tracker that would piggyback on the client's signal and work backwards all the way to the source and get me the IP address. But little did I know that Django already does that for me. The IP address and host name (ISP) is encoded in the request parameter. Let's see how to view them.
To do this we'll create a simple view. In HTML, we'll create a list that contains header name and value, and then populate it through Django.
headers.html
<html>
<head><title>Django HTTP headers</title></head>
<body>
<ul>
{% for header in headers %}
<li><b>{{ header.name }}</b>: {{ header.value }}</li>
{% endfor %}
</ul>
</body>
</html>
Pretty straightforward. Now let's populate the list.
views.py
from django.shortcuts import render
class Header (object):
def __init__ (self, name, value):
self.name, self.value = name, value
def headers (request):
headers = []
headers_list = request.META.items ()
for name, value in headers_list:
headers.append (Header (name, value))
return render (request, "headers.html", {"headers":headers})
Let's see what's going on here. First, we import the render function. Then, we create a class called Header for use in the templating language. We already saw this with Student in Django Templating Language - Part IV. Now, request.META contains a list of headers and its method items() returns a list of tuples with name and value. We use that to populate the list in HTML.
One more thing. Notice how I provided the context directly as a parameter in the render function call? You can do that too. There's no need to do the Template/Context schedule each time.
No comments:
Post a Comment