Middleware configuration in Django - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to add a middleware class to the Django settings.

Django

MIDDLEWARE = [
    'django.middleware.security.SecurityMiddleware',
    [1],
    'django.middleware.common.CommonMiddleware',
]

Drag options to blanks, or click blank then click option'

A'django.middleware.csrf.CsrfViewMiddleware'

B'django.middleware.clickjacking.XFrameOptionsMiddleware'

C'django.middleware.locale.LocaleMiddleware'

D'django.contrib.sessions.middleware.SessionMiddleware'

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing middleware unrelated to session management.

Forgetting to include quotes around the middleware path.

The SessionMiddleware manages sessions and should be included in the middleware list.

2fill in blank

medium

Complete the code to add a custom middleware class path to the settings.

Django

MIDDLEWARE += [
    [1]
]

Drag options to blanks, or click blank then click option'

A'myapp.middleware.CustomMiddleware'

B'django.middleware.common.CommonMiddleware'

C'django.middleware.security.SecurityMiddleware'

D'django.middleware.csrf.CsrfViewMiddleware'

Attempts:

3 left

💡 Hint

Common Mistakes

Using built-in middleware instead of custom middleware path.

Omitting quotes around the middleware path.

Custom middleware classes are added by specifying their full Python path as a string.

3fill in blank

hard

Fix the error in the middleware list by completing the missing middleware.

Django

MIDDLEWARE = [
    'django.middleware.security.SecurityMiddleware',
    'django.contrib.sessions.middleware.[1]',
    'django.middleware.common.CommonMiddleware',
]

Drag options to blanks, or click blank then click option'

ASessionMiddleware

BCsrfViewMiddleware

CLocaleMiddleware

DAuthenticationMiddleware

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing session middleware with CSRF middleware.

Using middleware from the wrong Django module.

The correct middleware class for session management is SessionMiddleware.

4fill in blank

hard

Fill both blanks to correctly configure middleware that handles authentication and CSRF protection.

Django

MIDDLEWARE = [
    [1],
    [2],
]

Drag options to blanks, or click blank then click option'

A'django.contrib.auth.middleware.AuthenticationMiddleware'

B'django.middleware.security.SecurityMiddleware'

C'django.middleware.csrf.CsrfViewMiddleware'

D'django.middleware.common.CommonMiddleware'

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up security middleware with authentication middleware.

Omitting CSRF middleware which is important for form security.

The AuthenticationMiddleware manages user authentication, and CsrfViewMiddleware protects against CSRF attacks.

5fill in blank

hard

Fill all three blanks to create a middleware list that includes security, session, and clickjacking protection.

Django

MIDDLEWARE = [
    [1],
    [2],
    [3],
]

Drag options to blanks, or click blank then click option'

A'django.middleware.security.SecurityMiddleware'

B'django.contrib.sessions.middleware.SessionMiddleware'

C'django.middleware.clickjacking.XFrameOptionsMiddleware'

D'django.middleware.common.CommonMiddleware'

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting to include session middleware.

Mixing up middleware order which can affect behavior.

This middleware list includes security features, session management, and protection against clickjacking attacks.

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