HttpRequest object in Django - Step-by-Step Execution

Concept Flow - HttpRequest object

Browser sends HTTP request

↓

Django receives request

↓

Create HttpRequest object

↓

Populate attributes (method, path, GET, POST, headers, etc.)

↓

Pass HttpRequest object to view function

↓

View reads HttpRequest data and returns HttpResponse

This flow shows how Django creates an HttpRequest object from a browser request and passes it to your view to handle.

Execution Sample

Django

from django.http import HttpResponse

def my_view(request):
    method = request.method
    path = request.path
    user_agent = request.headers.get('User-Agent')
    return HttpResponse(f"Method: {method}, Path: {path}, Agent: {user_agent}")

This view reads the HTTP method, path, and User-Agent header from the HttpRequest object and returns them in the response.

Execution Table

Step	Action	HttpRequest attribute accessed	Value extracted	Effect
1	Receive HTTP GET request to /home	method	GET	HttpRequest.method set to 'GET'
2	Access request.method in view	method	GET	Stores 'GET' in variable method
3	Access request.path in view	path	/home	Stores '/home' in variable path
4	Access request.headers.get('User-Agent')	headers['User-Agent']	Mozilla/5.0	Stores user agent string
5	Return HttpResponse with formatted string	N/A	N/A	Response body contains method, path, and agent info
6	End of view execution	N/A	N/A	HttpResponse sent to browser

💡 View finishes execution and returns HttpResponse to client

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
method	N/A	GET	GET	GET	GET
path	N/A	N/A	/home	/home	/home
user_agent	N/A	N/A	N/A	Mozilla/5.0	Mozilla/5.0

Key Moments - 3 Insights

Why does request.method contain 'GET' instead of the full HTTP request?

request.method holds only the HTTP method string (like 'GET') extracted from the full HTTP request, as shown in execution_table step 1 and 2.

How does request.headers.get('User-Agent') safely get the header?

Using .get() avoids errors if the header is missing, returning None instead. This is shown in execution_table step 4 where the header value is extracted.

Why do we access request.path instead of parsing the URL ourselves?

Django's HttpRequest.path gives the URL path directly, saving you from manual parsing, as seen in execution_table step 3.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'method' after step 2?

A Mozilla/5.0

B /home

C GET

D POST

💡 Hint

Check the 'Value extracted' column at step 2 in the execution_table.

At which step does the view access the URL path from the HttpRequest?

A Step 3

B Step 1

C Step 4

D Step 5

💡 Hint

Look for when 'path' is accessed in the 'HttpRequest attribute accessed' column.

If the 'User-Agent' header was missing, what would request.headers.get('User-Agent') return?

A An error is raised

B None

C An empty string ''

D The string 'User-Agent'

💡 Hint

Recall that .get() returns None if the key is missing, as explained in key_moments.

Concept Snapshot

HttpRequest object in Django:
- Created automatically for each HTTP request
- Contains attributes like method, path, GET, POST, headers
- Passed to view functions as 'request'
- Use request.method for HTTP method (GET, POST, etc.)
- Use request.path for URL path
- Use request.headers.get('Header-Name') to access headers safely

Full Transcript

When a browser sends an HTTP request, Django creates an HttpRequest object. This object holds details like the HTTP method, URL path, and headers. The HttpRequest is passed to your view function as the 'request' parameter. Inside the view, you can read request.method to know if it's GET or POST, request.path to get the URL path, and request.headers.get('User-Agent') to get the browser's user agent string. This lets your view respond based on the request details. The execution table shows each step accessing these attributes and how variables change. Using .get() on headers avoids errors if a header is missing. Finally, the view returns an HttpResponse with the gathered info.