Exception middleware in Django - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is exception middleware in Django?

Exception middleware is a special layer in Django that catches errors during request processing and lets you handle them gracefully, like showing a friendly error page instead of a crash.

intermediate

How do you create custom exception middleware in Django?

You create a class with a __call__ method that takes the request and calls the next layer. Inside, you use try-except to catch exceptions and handle them as you want.

beginner

Where do you add your exception middleware in Django settings?

You add your exception middleware class path to the MIDDLEWARE list in settings.py, usually near the top so it can catch errors early.

beginner

What happens if exception middleware does not catch an error?

If the exception middleware does not catch an error, Django's default error handling takes over, which usually shows a debug page in development or a generic error page in production.

beginner

Why is exception middleware useful in a Django project?

It helps keep your site running smoothly by catching unexpected errors, logging them, and showing user-friendly messages instead of crashing or showing confusing errors.

What method must a Django middleware class implement to handle requests and exceptions?

A __call__

B process_request

C handle_exception

D process_view

In modern Django middleware, the __call__ method is used to process requests and handle exceptions.

Where do you register your custom exception middleware in a Django project?

A In the MIDDLEWARE list in settings.py

B In urls.py

C In models.py

D In views.py

Middleware classes are registered in the MIDDLEWARE list inside settings.py.

What is the main purpose of exception middleware?

A To connect to the database

B To route URLs to views

C To render HTML templates

D To catch and handle errors during request processing

Exception middleware catches errors during request processing to handle them gracefully.

If an exception is not caught by your middleware, what does Django do?

A Ignores the error

B Shows default error handling pages

C Automatically fixes the error

D Restarts the server

Django shows default error pages if exceptions are not caught by middleware.

Which of these is a benefit of using exception middleware?

A Automatically writes views

B Speeds up database queries

C Improves user experience by showing friendly error messages

D Changes URL patterns

Exception middleware improves user experience by handling errors gracefully.

Explain how exception middleware works in Django and why it is important.

Think about how middleware acts like a safety net for errors.

Describe the steps to create and use custom exception middleware in a Django project.

Focus on coding the class and registering it.

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