WSGI middleware concept in Flask - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is WSGI middleware in the context of Flask?

WSGI middleware is a piece of code that sits between the web server and the Flask app. It can modify requests or responses, add features, or handle tasks before the app processes the request or after it sends the response.

beginner

How does WSGI middleware interact with a Flask application?

WSGI middleware wraps the Flask app. When a request comes in, it passes through the middleware first, which can change the request or do extra work, then it goes to the Flask app. The response from the app also passes back through the middleware before reaching the client.

beginner

Give a simple real-life analogy for WSGI middleware.

Think of WSGI middleware like a security guard at a building entrance. The guard checks or modifies what comes in or goes out before letting it pass. Similarly, middleware checks or changes web requests and responses before they reach the app or the user.

intermediate

What kind of tasks can WSGI middleware perform?

Middleware can do tasks like logging requests, handling authentication, compressing responses, or adding headers. It helps keep the Flask app code simple by handling these common tasks separately.

intermediate

How do you add WSGI middleware to a Flask app?

You wrap the Flask app with the middleware class or function. For example, if you have a middleware called MyMiddleware, you do: app = MyMiddleware(app). This makes the middleware handle requests before the Flask app.

What does WSGI middleware do in a Flask app?

A Replaces the Flask app completely

B Runs the Flask app without a server

C Only handles database connections

D Modifies requests and responses between the server and app

WSGI middleware sits between the server and Flask app to modify or handle requests and responses.

Where does WSGI middleware sit in the request flow?

A Between the web server and the Flask app

B After the Flask app sends the response

C Inside the Flask app code

D Only on the client side

Middleware sits between the web server and the Flask app, processing requests and responses.

Which of these is NOT a typical middleware task?

A Logging requests

B Handling authentication

C Rendering HTML templates

D Compressing responses

Rendering HTML templates is done inside the Flask app, not by middleware.

How do you apply middleware to a Flask app?

A By wrapping the Flask app with the middleware class or function

B By modifying the Flask app source code

C By importing it inside a route function

D By running middleware as a separate server

Middleware wraps the Flask app, so requests pass through it before reaching the app.

What is a simple analogy for WSGI middleware?

A A chef cooking food

B A security guard checking people at a door

C A taxi driving passengers

D A painter painting a wall

Middleware acts like a security guard checking or modifying requests before they enter the app.

Explain what WSGI middleware is and how it works with a Flask app.

Think about a middle step between the web server and your Flask code.

Describe a real-life example that helps you understand the role of WSGI middleware.

Imagine someone checking visitors before they enter a building.

Practice

1. What is the main role of WSGI middleware in a Flask application?

easy

A. To serve static files directly to the client

B. To replace the Flask app entirely

C. To sit between the server and the Flask app to modify requests or responses

D. To handle database connections automatically

Solution

1. Step 1: Understand WSGI middleware position

   WSGI middleware acts as a layer between the web server and the Flask app, intercepting requests and responses.

2. Step 2: Identify middleware purpose

   It modifies or adds features like logging or security without replacing the app or handling unrelated tasks.

3. Final Answer:

   To sit between the server and the Flask app to modify requests or responses -> Option C

4. Quick Check:

   Middleware = intercepts requests/responses [OK]

Hint: Middleware wraps app to add features between server and app [OK]

Common Mistakes:

• Thinking middleware replaces the app
• Confusing middleware with static file serving
• Assuming middleware manages database connections

2. Which of the following is the correct way to wrap a Flask app with WSGI middleware named MyMiddleware?

easy

A. app = MyMiddleware(app)

B. app = app.MyMiddleware()

C. MyMiddleware(app)

D. app.middleware = MyMiddleware

Solution

1. Step 1: Recall middleware wrapping syntax

   WSGI middleware wraps the Flask app by passing the app instance to the middleware constructor.

2. Step 2: Match correct syntax

   The correct syntax is assigning the wrapped app back to app using app = MyMiddleware(app).

3. Final Answer:

   app = MyMiddleware(app) -> Option A

4. Quick Check:

   Wrap app by passing it to middleware constructor [OK]

Hint: Wrap app by calling middleware with app as argument [OK]

Common Mistakes:

• Calling middleware as a method on app
• Not assigning wrapped app back to a variable
• Assigning middleware class without instantiation

3. Given this WSGI middleware code wrapping a Flask app, what will be printed when a request is made?

class SimpleMiddleware:
    def __init__(self, app):
        self.app = app
    def __call__(self, environ, start_response):
        print('Before app')
        response = self.app(environ, start_response)
        print('After app')
        return response

app = Flask(__name__)
app = SimpleMiddleware(app)

medium

A. No output is printed

B. Only Before app is printed

C. Only After app is printed

D. Before app printed before request, After app printed after request

Solution

1. Step 1: Analyze middleware call flow

   The middleware prints 'Before app' before calling the wrapped app, then prints 'After app' after the app returns.

2. Step 2: Understand request handling

   When a request comes, both print statements execute in order around the app call.

3. Final Answer:

   Before app printed before request, After app printed after request -> Option D

4. Quick Check:

   Middleware prints before and after app call [OK]

Hint: Middleware __call__ runs code before and after app call [OK]

Common Mistakes:

• Assuming only one print runs
• Thinking prints happen asynchronously
• Confusing middleware with Flask route handlers

4. Identify the error in this WSGI middleware implementation:

class BrokenMiddleware:
    def __init__(self, app):
        self.app = app
    def __call__(self, environ, start_response):
        # Forgot to call the wrapped app
        return 'Hello'

medium

A. Middleware must call the wrapped app and return its response

B. Middleware should not have an __init__ method

C. Middleware should return a Flask response object, not a string

D. Middleware must not accept environ and start_response parameters

Solution

1. Step 1: Check middleware call method

   The __call__ method must call the wrapped app with environ and start_response to get the response.

2. Step 2: Identify missing call

   This code returns a string directly and does not call the wrapped app, breaking the WSGI chain.

3. Final Answer:

   Middleware must call the wrapped app and return its response -> Option A

4. Quick Check:

   Middleware must call wrapped app [OK]

Hint: Middleware must call and return wrapped app response [OK]

Common Mistakes:

• Returning a string instead of calling app
• Removing __init__ method unnecessarily
• Misunderstanding WSGI call signature

5. You want to add a WSGI middleware to your Flask app that adds a custom header X-Custom-Header: Hello to every response. Which approach correctly implements this?

hard

A. Wrap the app and modify the start_response to add the header after calling the app

B. Wrap the app and modify the start_response to add the header before calling the app

C. Modify the Flask app routes to add the header manually in each view

D. Add the header in the middleware by modifying the response iterable directly without start_response

Solution

1. Step 1: Understand start_response role

   start_response is a callable that sets HTTP status and headers before the response body is sent.

2. Step 2: Add header by wrapping start_response

   Middleware should wrap start_response to add the custom header before passing it to the app, so when the app calls it, the header is added.

3. Final Answer:

   Wrap the app and modify the start_response to add the header before calling the app -> Option B

4. Quick Check:

   Add headers by wrapping start_response before app call [OK]

Hint: Wrap start_response to add headers before app call [OK]

Common Mistakes:

• Adding headers after calling app (too late, start_response already called by app)
• Modifying response iterable directly (not standard for headers)
• Changing all routes instead of middleware