Exception middleware in Django - Step-by-Step Execution

Concept Flow - Exception middleware

Request received

↓

Middleware process_request

↓

View function called

↓

Exception occurs?

No→Response returned

Yes↓

Middleware process_exception

↓

Handle exception or re-raise

↓

Response returned

This flow shows how Django middleware catches exceptions during request processing and handles them before sending a response.

Execution Sample

Django

from django.http import HttpResponse

class ExceptionMiddleware:
    def __init__(self, get_response):
        self.get_response = get_response

    def __call__(self, request):
        try:
            response = self.get_response(request)
        except Exception as e:
            response = self.process_exception(request, e)
        return response

    def process_exception(self, request, exception):
        return HttpResponse('Error caught by middleware')

This middleware catches exceptions from views and returns a custom error response.

Execution Table

Step	Action	Evaluation	Result
1	Request received	N/A	Request object created
2	Middleware __call__ starts	N/A	Ready to call get_response
3	Call get_response(request)	View runs	Exception raised: ValueError
4	Exception caught in except block	Exception is ValueError	Call process_exception
5	process_exception(request, exception)	Return HttpResponse	Custom error response created
6	Return response	Response ready	Response sent to client

💡 Exception caught and handled by middleware, response returned instead of error

Variable Tracker

Variable	Start	After Step 3	After Step 5	Final
request	Request object	Request object	Request object	Request object
response	None	Exception raised, no response yet	HttpResponse('Error caught by middleware')	HttpResponse('Error caught by middleware')
exception	None	ValueError instance	ValueError instance	ValueError instance

Key Moments - 2 Insights

Why does the middleware catch the exception instead of letting Django handle it?

Because the middleware wraps the view call in a try-except block (see execution_table step 3 and 4), it intercepts exceptions and can return a custom response.

What happens if process_exception does not return a response?

If process_exception returns None, Django continues processing other middleware or default error handling. Here, it returns a response (step 5), so processing stops.

Visual Quiz - 3 Questions

Look at the execution table, at which step is the exception caught?

A Step 4

B Step 3

C Step 5

D Step 6

💡 Hint

Check the 'Action' and 'Evaluation' columns in step 4 where the exception is caught.

According to variable_tracker, what is the value of 'response' after step 3?

A HttpResponse object

B None

C Exception instance

D Request object

💡 Hint

Look at the 'response' row under 'After Step 3' in variable_tracker.

If process_exception returned None, what would happen to the response?

A Response would be the original successful view response

B Middleware would return None and cause an error

C Django would continue default exception handling

D Exception would be ignored silently

💡 Hint

Recall key_moments explanation about process_exception return values.

Concept Snapshot

Exception middleware in Django wraps view calls in try-except.
If an exception occurs, process_exception handles it.
It can return a custom HttpResponse to avoid server errors.
If None is returned, Django continues default error handling.
This helps gracefully manage errors in web requests.

Full Transcript

In Django, exception middleware intercepts errors during request processing. When a request comes in, the middleware calls the next layer (usually the view). If the view raises an exception, the middleware catches it in a try-except block. Then it calls process_exception to handle the error. This method can return a custom response, like an error message, instead of letting the server crash. If process_exception returns None, Django will handle the error normally. This flow helps developers control error responses and improve user experience.

Practice

1. What is the main purpose of exception middleware in Django?

easy

A. To catch errors during request processing and handle them gracefully

B. To speed up database queries

C. To serve static files like images and CSS

D. To manage user authentication sessions

Solution

1. Step 1: Understand middleware role

   Middleware processes requests and responses in Django, and exception middleware specifically handles errors.

2. Step 2: Identify exception middleware purpose

   Its job is to catch exceptions during request handling and provide friendly error messages or logging.

3. Final Answer:

   To catch errors during request processing and handle them gracefully -> Option A

4. Quick Check:

   Exception middleware = catch errors [OK]

Hint: Exception middleware catches errors in requests [OK]

Common Mistakes:

• Confusing middleware with static file serving
• Thinking it manages database queries
• Assuming it handles user sessions

2. Which method must be implemented in a Django exception middleware class to process requests?

easy

A. __init__

B. __call__

C. process_exception

D. handle_request

Solution

1. Step 1: Recall middleware structure

   Django middleware classes require an __init__ and a __call__ method to be callable.

2. Step 2: Identify request processing method

   The __call__ method is called for each request and is where exception handling happens.

3. Final Answer:

   __call__ -> Option B

4. Quick Check:

   Request processing method = __call__ [OK]

Hint: Middleware uses __call__ to handle requests [OK]

Common Mistakes:

• Choosing process_exception which is for old-style middleware
• Confusing __init__ as request handler
• Inventing non-existent handle_request method

3. Given this middleware snippet, what will be the output if a ZeroDivisionError occurs during request processing?

class ExceptionMiddleware:
    def __init__(self, get_response):
        self.get_response = get_response

    def __call__(self, request):
        try:
            response = self.get_response(request)
        except ZeroDivisionError:
            return HttpResponse('Division error caught')
        return response

medium

A. The original response from get_response

B. A server error 500 page

C. No response, request hangs

D. HttpResponse with text 'Division error caught'

Solution

1. Step 1: Analyze try-except block

   The middleware calls get_response inside try; if ZeroDivisionError occurs, it returns a custom HttpResponse.

2. Step 2: Determine output on error

   When ZeroDivisionError happens, the except block returns HttpResponse('Division error caught').

3. Final Answer:

   HttpResponse with text 'Division error caught' -> Option D

4. Quick Check:

   Error caught returns custom response [OK]

Hint: Exception triggers except block response [OK]

Common Mistakes:

• Assuming original response is returned despite error
• Expecting default 500 error page
• Thinking request will hang without response

4. Identify the error in this exception middleware code:

class ExceptionMiddleware:
    def __init__(self, get_response):
        self.get_response = get_response

    def __call__(self, request):
        try:
            response = self.get_response(request)
        except Exception as e:
            print('Error:', e)
        return response

medium

A. No __init__ method defined

B. Incorrect method name __call__

C. Missing return statement inside except block

D. Using print instead of logging

Solution

1. Step 1: Check exception handling flow

   If an exception occurs, except block prints error but does not return a response.

2. Step 2: Understand middleware response requirement

   Middleware must always return a response; missing return in except causes NameError or no response.

3. Final Answer:

   Missing return statement inside except block -> Option C

4. Quick Check:

   Exception block must return response [OK]

Hint: Always return response in except block [OK]

Common Mistakes:

• Ignoring missing return causes runtime error
• Thinking print is enough for error handling
• Confusing method names or missing __init__

5. You want to create exception middleware that logs errors and returns a JSON error response with status 500. Which code snippet correctly implements this behavior?

import json
from django.http import HttpResponse

class ExceptionMiddleware:
    def __init__(self, get_response):
        self.get_response = get_response

    def __call__(self, request):
        try:
            response = self.get_response(request)
        except Exception as e:
            # Log the error
            print(f'Error: {e}')
            # Return JSON error response
            error_content = json.dumps({'error': 'Server error'})
            return HttpResponse(error_content, content_type='application/json', status=500)
        return response

hard

A. Correctly logs error and returns JSON response with status 500

B. Does not log error, only returns JSON response

C. Returns HTML response instead of JSON

D. Raises exception instead of handling it

Solution

1. Step 1: Check error logging

   The except block prints the error, which acts as logging here.

2. Step 2: Verify JSON response and status

   It returns HttpResponse with JSON content, correct content_type, and status 500.

3. Final Answer:

   Correctly logs error and returns JSON response with status 500 -> Option A

4. Quick Check:

   Logs error + JSON 500 response [OK]

Hint: Print error then return JSON with status 500 [OK]

Common Mistakes:

• Forgetting to set content_type to application/json
• Not returning response in except block
• Raising exception instead of handling