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.

Practice

1. In Django, what is the first step when a user visits a website URL?

easy

A. Django directly renders the template without processing.

B. Django matches the URL to a view using URL patterns.

C. Django sends data to the database.

D. Django executes JavaScript on the client side.

Solution

1. Step 1: Understand URL routing in Django

   Django uses URL patterns defined in urls.py to find which view should handle the request.

2. Step 2: Identify the first action on a request

   The first action is matching the URL to a view, not rendering or database access.

3. Final Answer:

   Django matches the URL to a view using URL patterns. -> Option B

4. Quick Check:

   URL routing = matching URL to view [OK]

Hint: Remember: URL first matches view, then view handles data [OK]

Common Mistakes:

• Thinking template renders before view runs
• Assuming database is accessed before URL matching
• Confusing client-side JavaScript with Django server process

2. Which of the following is the correct way to define a URL pattern in Django's urls.py?

easy

A. path('home/', views.home_view, name='home')

B. url('home/', views.home_view)

C. route('home/', views.home_view)

D. link('home/', views.home_view)

Solution

1. Step 1: Recall Django URL pattern syntax

   Django 3+ uses path() to define URL patterns, with URL string, view function, and optional name.

2. Step 2: Identify correct function name

   url() is deprecated, and route() or link() are invalid.

3. Final Answer:

   path('home/', views.home_view, name='home') -> Option A

4. Quick Check:

   Use path() for URL patterns [OK]

Hint: Use path() in urls.py, not url() or other names [OK]

Common Mistakes:

• Using deprecated url() instead of path()
• Using non-existent functions like route() or link()
• Omitting the view function argument

3. Given this view function, what will be the rendered output if the template displays {{ message }}?

def hello_view(request):
    context = {'message': 'Hello, Django!'}
    return render(request, 'hello.html', context)

medium

A. Hello, Django!

B. context

C. hello.html

D. request

Solution

1. Step 1: Understand context passing in Django views

   The view passes a dictionary with key 'message' and value 'Hello, Django!' to the template.

2. Step 2: Template renders variable from context

   The template uses {{ message }} to display the value 'Hello, Django!'.

3. Final Answer:

   Hello, Django! -> Option A

4. Quick Check:

   Template variable = context value [OK]

Hint: Template {{ var }} shows context['var'] value [OK]

Common Mistakes:

• Confusing template name with output
• Thinking context dictionary prints as string
• Assuming request object is shown in template

4. What is wrong with this Django view function?

def my_view(request):
    return render('my_template.html')

medium

A. The function name must be capitalized.

B. The template name should be a dictionary.

C. The view should return HttpResponseRedirect instead.

D. The render function is missing the request argument.

Solution

1. Step 1: Check render function signature

   render() requires at least two arguments: request and template name.

2. Step 2: Identify missing argument

   The code only passes the template name, missing the request argument.

3. Final Answer:

   The render function is missing the request argument. -> Option D

4. Quick Check:

   render(request, template) needs request first [OK]

Hint: render() always needs request as first argument [OK]

Common Mistakes:

• Forgetting to pass request to render()
• Thinking template name should be a dict
• Confusing render with redirect functions

5. You want to display a list of products on a page. Which sequence correctly describes how Django processes this request? A user visits /products/. The URL pattern matches products_view. The view fetches products from the database and passes them to products.html template. The template shows the product names in a list. Which is the correct order of steps Django follows internally?

hard

A. View fetches data -> URL matches -> Template renders -> Response sent

B. Template renders -> View fetches data -> URL matches -> Response sent

C. URL -> View fetches data -> Template renders with data -> Response sent

D. Response sent -> URL matches -> View fetches data -> Template renders

Solution

1. Step 1: URL matching

   Django first matches the incoming URL to the correct view function using URL patterns.

2. Step 2: View processes request

   The view fetches data (products) from the database and prepares context for the template.

3. Step 3: Template rendering and response

   The template uses the context to render HTML, which Django sends as the HTTP response.

4. Final Answer:

   URL -> View fetches data -> Template renders with data -> Response sent -> Option C

5. Quick Check:

   URL then view then template then response [OK]

Hint: Remember: URL matches first, then view, then template, then response [OK]

Common Mistakes:

• Thinking template renders before URL matching
• Mixing order of view and URL matching
• Assuming response sent before processing