Why middleware extends functionality in Flask - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does middleware enhance a Flask app?

Middleware in Flask is used to add extra steps during request processing. What is the main way middleware extends functionality?

A By changing the HTML templates after they are rendered

B By replacing the Flask app's core routing system entirely

C By directly modifying the database schema used by the app

D By intercepting requests and responses to add or modify data before reaching the route or client

💡 Hint

Think about what middleware can do between the client and the route handler.

Middleware acts like a checkpoint that can inspect or change requests and responses. It does not replace routing or directly change databases or templates but can add features like logging, authentication, or headers.

❓ component_behavior

intermediate

What output results from this Flask middleware example?

Given this Flask middleware that adds a header, what will the client receive in the response headers?

Flask

from flask import Flask, request

app = Flask(__name__)

@app.before_request
def before():
    print('Before request')

@app.after_request
def after(response):
    response.headers['X-Custom'] = 'Middleware'
    return response

@app.route('/')
def home():
    return 'Hello'

# Client sends GET /

A Response includes header 'X-Custom' with value 'Middleware'

B Server raises an error due to missing middleware

C Response has no 'X-Custom' header

D Response includes header 'X-Custom' with value 'Hello'

💡 Hint

Look at the after_request function modifying headers.

The after_request function adds a custom header 'X-Custom' with value 'Middleware' to every response before sending it to the client.

❓ lifecycle

advanced

At which point does middleware run in Flask's request lifecycle?

Consider Flask's request lifecycle. When does middleware typically execute to extend functionality?

A Only inside the route function itself

B Only after the response is sent to the client

C Before the route function is called and after the response is created

D Only during app startup before any requests

💡 Hint

Middleware can act both before and after route processing.

Middleware hooks like before_request and after_request run before the route handler and after the response is generated, allowing modification at both stages.

🔧 Debug

advanced

Why does this Flask middleware not add the header as expected?

This middleware tries to add a header but the client never sees it. What is the likely cause? @app.after_request def add_header(response): response.headers['X-Test'] = 'Value' # Missing return statement here @app.route('/') def index(): return 'Hi'

A Headers cannot be added in after_request, only before_request

B The after_request function must return the response object to apply changes

C The route must explicitly add the header, middleware cannot

D Flask does not support custom headers

💡 Hint

Check what the after_request function returns.

after_request functions must return the response object. Without returning it, Flask sends the original response without the header changes.

📝 Syntax

expert

Which middleware code snippet correctly modifies request data in Flask?

You want to add a custom attribute to the request object in Flask middleware. Which snippet is correct?

A

@app.before_request
def modify_request():
    request.custom = 'data'

B

@app.after_request
def modify_request(response):
    request.custom = 'data'
    return response

C

@app.before_request
def modify_request():
    request = 'data'

D

@app.before_request
def modify_request():
    request.headers['custom'] = 'data'

💡 Hint

Remember how to add attributes to Flask's request object safely.

Option A correctly adds a new attribute to the request object before the route runs. Option A tries to modify request after response, which is too late. Option A reassigns request, breaking it. Option A tries to modify immutable headers.