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.