Middleware configuration in Django - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is middleware in Django?

Middleware is a way to process requests and responses globally before they reach the view or after the view has processed them. It acts like a chain of functions that can modify input or output.

beginner

Where do you configure middleware in a Django project?

Middleware is configured in the MIDDLEWARE list inside the settings.py file of a Django project.

intermediate

How does the order of middleware in the MIDDLEWARE list affect request processing?

Middleware is processed in the order listed for requests (top to bottom) and in reverse order for responses (bottom to top). So, order matters for how middleware interacts.

intermediate

How do you add a custom middleware in Django?

Create a middleware class with <code>__init__</code>, <code>__call__</code>, or specific methods like <code>process_request</code>. Then add its full Python path to the <code>MIDDLEWARE</code> list in <code>settings.py</code>.

beginner

What is a common use case for middleware in Django?

Common uses include handling authentication, logging requests, modifying response headers, or managing sessions globally across the app.

Where is the middleware list configured in a Django project?

A In the <code>models.py</code> file

B In the <code>settings.py</code> file under <code>MIDDLEWARE</code>

C In the <code>urls.py</code> file

D In the <code>views.py</code> file

Middleware is configured in the MIDDLEWARE list inside settings.py.

What happens first when a request comes in Django with multiple middleware?

A Middleware are processed top to bottom in the <code>MIDDLEWARE</code> list

B Middleware are processed bottom to top in the <code>MIDDLEWARE</code> list

C Only the last middleware runs

D Middleware order does not matter

Requests pass through middleware in the order they are listed (top to bottom).

How do you add a custom middleware to your Django project?

A Add it to <code>INSTALLED_APPS</code>

B Create a new app and name it middleware

C Add the middleware class path to the <code>MIDDLEWARE</code> list in <code>settings.py</code>

D Write middleware code inside <code>views.py</code>

Custom middleware must be added to the MIDDLEWARE list in settings.py.

Which of these is NOT a typical middleware use case?

A Defining database models

B Logging requests and responses

C Handling authentication globally

D Modifying response headers

Defining database models is done in models.py, not middleware.

In what order are middleware processed for responses?

A Only the first middleware processes responses

B Top to bottom of the <code>MIDDLEWARE</code> list

C Random order

D Bottom to top of the <code>MIDDLEWARE</code> list

Responses pass through middleware in reverse order (bottom to top).

Explain how middleware works in Django and how you configure it.

Think about the path a request takes through middleware before reaching views.

Describe a simple example of a custom middleware and how you add it to a Django project.

Focus on the steps from writing code to activating middleware.

Practice

1. What is the purpose of middleware in a Django project?

easy

A. To create HTML templates

B. To process requests and responses globally before reaching views

C. To define database models

D. To manage user sessions only

Solution

1. Step 1: Understand middleware role

   Middleware runs code on every request and response, acting globally.

2. Step 2: Compare with other options

   Models define data, templates create HTML, sessions are part of middleware but not the only role.

3. Final Answer:

   To process requests and responses globally before reaching views -> Option B

4. Quick Check:

   Middleware = global request/response processing [OK]

Hint: Middleware acts on all requests and responses [OK]

Common Mistakes:

• Confusing middleware with models or templates
• Thinking middleware only manages sessions
• Assuming middleware runs only after views

2. Which of the following is the correct way to add a middleware class in Django's settings.py?

easy

A. 'django.middleware.security.SecurityMiddleware',

B. django.middleware.security.SecurityMiddleware

C. 'SecurityMiddleware',

D. SecurityMiddleware

Solution

1. Step 1: Check syntax for middleware entry

   Middleware classes must be strings with full Python path and comma-separated in list.

2. Step 2: Validate options

   'django.middleware.security.SecurityMiddleware', is a string with full path and comma, correct syntax. Others miss quotes or full path.

3. Final Answer:

   'django.middleware.security.SecurityMiddleware', -> Option A

4. Quick Check:

   Middleware entries are full strings with commas [OK]

Hint: Middleware must be full string path with quotes and comma [OK]

Common Mistakes:

• Omitting quotes around middleware path
• Using only class name without module path
• Missing commas between middleware entries

3. Given this MIDDLEWARE list in settings.py:

[  'django.middleware.security.SecurityMiddleware',  'django.contrib.sessions.middleware.SessionMiddleware',  'django.middleware.common.CommonMiddleware',]

Which middleware runs first on an incoming request?

medium

A. SessionMiddleware

B. CommonMiddleware

C. SecurityMiddleware

D. All run simultaneously

Solution

1. Step 1: Understand middleware order on request

   Middleware runs in the order listed for requests, first listed runs first.

2. Step 2: Identify first middleware in list

   SecurityMiddleware is first, so it runs first on incoming requests.

3. Final Answer:

   SecurityMiddleware -> Option C

4. Quick Check:

   Request middleware order = list order [OK]

Hint: First middleware in list runs first on requests [OK]

Common Mistakes:

• Thinking middleware runs in reverse order on requests
• Assuming all middleware run at the same time
• Confusing request and response middleware order

4. You added a custom middleware class to MIDDLEWARE but Django raises an error on startup. What is a common cause?

medium

A. Middleware class is not a string in MIDDLEWARE list

B. Middleware class missing required methods like __call__ or __init__

C. Middleware class is listed after django.middleware.common.CommonMiddleware

D. Middleware class is defined inside views.py

Solution

1. Step 1: Check middleware list format

   Middleware entries must be strings with full Python path, not class objects.

2. Step 2: Identify common mistake

   Adding the class object instead of string path causes Django startup error.

3. Final Answer:

   Middleware class is not a string in MIDDLEWARE list -> Option A

4. Quick Check:

   MIDDLEWARE entries must be strings [OK]

Hint: Middleware list must contain strings, not class objects [OK]

Common Mistakes:

• Adding middleware as class instead of string path
• Placing middleware in wrong order causing errors
• Defining middleware in wrong file without import

5. You want to add a middleware that modifies the response headers after all other middleware have processed the response. Where should you place it in the MIDDLEWARE list?

hard

A. At the end of the list

B. Right before django.middleware.common.CommonMiddleware

C. Anywhere, order does not matter for response

D. At the beginning of the list

Solution

1. Step 1: Understand middleware response order

   Middleware processes responses in reverse order of the list.

2. Step 2: Place middleware for last response processing

   To modify response after all other middleware (run last on response phase), place at beginning of list since first in list runs last on response.

3. Final Answer:

   At the beginning of the list -> Option D

4. Quick Check:

   Response middleware order = reverse list order [OK]

Hint: First in list runs last on response, put first for final changes [OK]

Common Mistakes:

• Placing middleware at end expecting last response run
• Assuming request and response order are the same
• Ignoring middleware order effects on response