Async middleware in Django - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of this async middleware logging example?

Consider this Django async middleware that logs request and response types. What will be printed in the console when a request is processed?

Django

import asyncio
from django.utils.deprecation import MiddlewareMixin

class AsyncLoggingMiddleware:
    async def __call__(self, request):
        print(f"Request type: {type(request)}")
        response = await self.get_response(request)
        print(f"Response type: {type(response)}")
        return response

A Request type: <class 'asyncio.Future'>\nResponse type: <class 'asyncio.Future'>

B Request type: <class 'django.http.HttpRequest'>\nResponse type: <class 'asyncio.coroutine'>

C Request type: <class 'django.http.HttpRequest'>\nResponse type: <class 'django.http.HttpResponse'>

D Request type: <class 'django.http.HttpResponse'>\nResponse type: <class 'django.http.HttpResponse'>

💡 Hint

Remember that Django passes HttpRequest objects to middleware and expects HttpResponse objects back.

The middleware receives a HttpRequest object and awaits the response, which is a HttpResponse object. The types printed reflect these classes.

📝 Syntax

intermediate

Which async middleware definition is syntactically correct in Django?

Select the option that correctly defines an async middleware class in Django 4+.

A

class MyMiddleware(MiddlewareMixin):
    async def __call__(self, request):
        response = self.get_response(request)
        return response

B

class MyMiddleware:
    async def __call__(self, request):
        response = await self.get_response(request)
        return response

C

class MyMiddleware:
    def __call__(self, request):
        response = await self.get_response(request)
        return response

D

class MyMiddleware:
    async def process_request(self, request):
        response = await self.get_response(request)
        return response

💡 Hint

Async middleware must define an async __call__ method and await the response.

Option B correctly defines an async __call__ method and awaits get_response. Option B is sync and does not await. Option B uses await in a sync method causing syntax error. Option B uses process_request which is not async middleware pattern.

🔧 Debug

advanced

Why does this async middleware cause a runtime error?

Given this middleware code, what is the cause of the runtime error when processing requests asynchronously? class FaultyMiddleware: def __call__(self, request): response = self.get_response(request) return response

A The __call__ method is not async but calls an async get_response without awaiting, causing a coroutine not awaited error.

B The middleware class is missing the MiddlewareMixin base class causing attribute errors.

C The get_response method is not defined in the middleware causing an AttributeError.

D The middleware uses sync __call__ but the request object is async-only causing a TypeError.

💡 Hint

Check if async functions are awaited properly in sync methods.

The get_response callable is async in async middleware chains. Calling it without await in a sync __call__ method returns a coroutine that is never awaited, causing runtime errors.

❓ state_output

advanced

What is the final value of request.state['count'] after this async middleware chain?

Two async middlewares increment a counter in request.state. What is the final count after processing a request? Middleware1: async def __call__(self, request): request.state['count'] = request.state.get('count', 0) + 1 response = await self.get_response(request) return response Middleware2: async def __call__(self, request): request.state['count'] = request.state.get('count', 0) + 1 response = await self.get_response(request) return response

A 2

B 1

C Raises KeyError because request.state is not initialized

D 0

💡 Hint

Each middleware increments the count once before passing the request on.

Both middlewares increment the count by 1. The first sets count=1, then calls next middleware which sets count=2. So final count is 2.

🧠 Conceptual

expert

Which statement best describes async middleware behavior in Django 4+?

Choose the most accurate statement about async middleware in Django 4 and later versions.

A Async middleware must inherit from MiddlewareMixin to work correctly with async views.

B Async middleware can only call async views; sync views cause runtime errors if called from async middleware.

C Async middleware cannot modify the request object because it is immutable during async processing.

D Async middleware must define an async __call__ method and can call both sync and async views seamlessly by awaiting get_response.

💡 Hint

Think about how Django handles sync and async views with async middleware.

Django's async middleware can await get_response which adapts to sync or async views internally, allowing seamless calling of both types.

Practice

1. What is the main benefit of using async middleware in Django?

easy

A. It allows Django to handle requests without waiting, improving speed.

B. It automatically caches all responses for faster loading.

C. It replaces the need for database queries.

D. It disables middleware for static files.

Solution

1. Step 1: Understand async middleware purpose

   Async middleware lets Django process requests without blocking, so it can handle other tasks simultaneously.

2. Step 2: Compare options

   Only It allows Django to handle requests without waiting, improving speed. correctly describes this benefit. Options A, C, and D describe unrelated or incorrect behaviors.

3. Final Answer:

   It allows Django to handle requests without waiting, improving speed. -> Option A

4. Quick Check:

   Async middleware improves speed by non-blocking handling [OK]

Hint: Async means non-blocking, so it improves request handling speed [OK]

Common Mistakes:

• Thinking async middleware caches responses
• Confusing async middleware with database optimization
• Assuming async disables middleware for static files

2. Which of the following is the correct way to define an async middleware __call__ method in Django?

easy

A. async def __call__(self, request): response = await self.get_response(request); return response

B. def __call__(self, request): response = await self.get_response(request); return response

C. def __call__(self, request): return self.get_response(request)

D. async def __call__(self, request): return self.get_response(request)

Solution

1. Step 1: Identify async method syntax

   The method must be declared with async def to use await inside.

2. Step 2: Check usage of await

   Only async def __call__(self, request): response = await self.get_response(request); return response correctly uses await with self.get_response(request) inside an async method.

3. Final Answer:

   async def __call__(self, request): response = await self.get_response(request); return response -> Option A

4. Quick Check:

   Async method with await = async def __call__(self, request): response = await self.get_response(request); return response [OK]

Hint: Async methods need async def and await inside [OK]

Common Mistakes:

• Using await inside a non-async function
• Missing await when calling async get_response
• Defining __call__ without async keyword

3. Given this async middleware snippet, what will be printed when a request is processed?

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

    async def __call__(self, request):
        print('Before response')
        response = await self.get_response(request)
        print('After response')
        return response

medium

A. No output printed due to async

B. Only Before response printed, then returns

C. Only After response printed, then returns

D. Before response printed, then After response printed after response

Solution

1. Step 1: Analyze print statements order

   The middleware prints 'Before response' before awaiting the response, then prints 'After response' after awaiting.

2. Step 2: Understand async call flow

   Await pauses until response is ready, so both prints happen in order around the response.

3. Final Answer:

   Before response printed, then After response printed after response -> Option D

4. Quick Check:

   Print before and after await = Before response printed, then After response printed after response [OK]

Hint: Print before and after await shows both messages in order [OK]

Common Mistakes:

• Thinking async prevents print output
• Assuming only one print runs
• Confusing order of prints around await

4. Identify the error in this async middleware code:

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

    async def __call__(self, request):
        response = self.get_response(request)
        response['X-Custom'] = 'Value'
        return response

medium

A. Async __call__ cannot return response

B. Cannot modify response headers in middleware

C. Missing await before self.get_response(request)

D. Missing async keyword in __init__

Solution

1. Step 1: Check async call to get_response

   Since __call__ is async, get_response must be awaited if it returns a coroutine.

2. Step 2: Identify missing await

   The code calls self.get_response(request) without await, causing a coroutine object instead of response.

3. Final Answer:

   Missing await before self.get_response(request) -> Option C

4. Quick Check:

   Async call needs await before get_response [OK]

Hint: Await async calls inside async methods [OK]

Common Mistakes:

• Forgetting await on async get_response
• Thinking response headers can't be changed
• Adding async to __init__ method

5. You want to create async middleware that adds a custom header only if the response status is 200. Which code snippet correctly implements this?

hard

A. async def __call__(self, request):
response = await self.get_response(request)
response['X-Status'] = 'OK'
return response

B. async def __call__(self, request):
response = await self.get_response(request)
if response.status_code == 200:
response['X-Status'] = 'OK'
return response

C. async def __call__(self, request):
response = self.get_response(request)
if response.status_code == 200:
response['X-Status'] = 'OK'
return response

D. def __call__(self, request):
response = self.get_response(request)
if response.status_code == 200:
response['X-Status'] = 'OK'
return response

Solution

1. Step 1: Confirm async __call__ and await usage

   The method must be async and await the get_response call to get the response object.

2. Step 2: Check conditional header addition

   Only async def __call__(self, request): response = await self.get_response(request) if response.status_code == 200: response['X-Status'] = 'OK' return response adds the header conditionally when status_code is 200, matching the requirement.

3. Final Answer:

   async def __call__(self, request): response = await self.get_response(request); if response.status_code == 200: response['X-Status'] = 'OK'; return response -> Option B

4. Quick Check:

   Async call with await and conditional header = async def __call__(self, request): response = await self.get_response(request) if response.status_code == 200: response['X-Status'] = 'OK' return response [OK]

Hint: Use async def with await and check status before adding header [OK]

Common Mistakes:

• Not awaiting get_response in async method
• Adding header unconditionally
• Defining __call__ as sync when async needed