How Django processes a request (URL → View → Template) - Visual Walkthrough

Concept Flow - How Django processes a request (URL → View → Template)

Browser sends URL request

↓

Django URL Dispatcher

↓

Match URL pattern to View

↓

Call View function/class

↓

View processes data

↓

Render Template with context

↓

Send HTML response back to Browser

This flow shows how Django takes a web request URL, finds the right view, processes data, renders a template, and sends back the HTML page.

Execution Sample

Django

from django.urls import path
from django.shortcuts import render

urlpatterns = [
    path('home/', home_view),
]

def home_view(request):
    return render(request, 'home.html', {'name': 'Alice'})

This code matches the URL '/home/' to home_view, which renders 'home.html' with a name variable.

Execution Table

Step	Action	Input/Condition	Result/Output
1	Receive HTTP request	URL = '/home/'	Request object created with URL '/home/'
2	URL Dispatcher checks patterns	Match 'home/' pattern?	Pattern matched to home_view
3	Call home_view function	Pass request object	Prepare context {'name': 'Alice'}
4	Render template 'home.html'	Context {'name': 'Alice'}	Generate HTML with name replaced
5	Send HTTP response	HTML content	Browser receives rendered HTML page

💡 Request processed fully; response sent back to browser

Variable Tracker

Variable	Start	After Step 3	After Step 4	Final
request	None	Request object with URL '/home/'	Same request object	Same request object
context	None	{'name': 'Alice'}	{'name': 'Alice'}	{'name': 'Alice'}
response	None	None	Rendered HTML string	HTTP response with HTML content

Key Moments - 3 Insights

How does Django know which view to call for a URL?

Django checks the URL patterns in order and calls the view linked to the first pattern that matches the request URL, as shown in step 2 of the execution table.

What does the view function do with the context data?

The view prepares a context dictionary with data (like {'name': 'Alice'}) and passes it to the template renderer, as seen in step 3 and 4.

When is the HTML actually created?

HTML is generated during template rendering in step 4, where the template placeholders are replaced with context data.

Visual Quiz - 3 Questions

Look at the execution table, what is the result after step 2?

A Pattern matched to home_view

B HTML page sent to browser

C Request object created

D Template rendered

💡 Hint

Check the 'Result/Output' column in step 2 of the execution table

At which step is the context {'name': 'Alice'} created?

A Step 1

B Step 4

C Step 3

D Step 5

💡 Hint

Look at the 'Action' and 'Result/Output' columns in step 3

If the URL did not match any pattern, what would change in the execution table?

A Step 5 would send a different HTML page

B Step 2 would show no match and no view called

C Step 4 would render a different template

D Step 3 would prepare a default context

💡 Hint

Think about what happens if URL Dispatcher finds no matching pattern in step 2

Concept Snapshot

Django request flow:
1. Browser sends URL request.
2. URL Dispatcher matches URL to a view.
3. View processes request and prepares context.
4. Template renders HTML using context.
5. Response with HTML sent back to browser.

Full Transcript

When a browser sends a URL request to Django, the URL Dispatcher checks the URL patterns to find a matching view. Once it finds the right view, Django calls that view function or class, passing the request object. The view prepares any data needed and passes it as context to a template. The template engine then renders the HTML page by replacing placeholders with context data. Finally, Django sends the rendered HTML back to the browser as a response. This process ensures that each URL shows the correct page with dynamic content.