Why middleware extends functionality in Flask

Introduction

Middleware helps add extra features to your web app without changing its main code. It acts like a helper that works between the user and your app.

You want to check user login before letting them see a page.

You need to log every request a user makes to your app.

You want to add security checks like blocking bad users.

You want to modify requests or responses, like adding headers.

You want to handle errors in one place for all requests.

Syntax

Flask

from flask import Flask, request

app = Flask(__name__)

@app.before_request
def middleware_function():
    # Code here runs before each request
    pass

@app.after_request
def after_middleware(response):
    # Code here runs after each request
    return response

@app.before_request runs code before each request reaches your route.

@app.after_request runs code after your route sends a response.

Examples

This middleware checks if the request has an Authorization header. If not, it stops the request with a 401 error.

Flask

from flask import Flask, request

app = Flask(__name__)

@app.before_request
def check_auth():
    if not request.headers.get('Authorization'):
        return 'Unauthorized', 401

This middleware adds a custom header to every response sent by the app.

Flask

from flask import Flask

app = Flask(__name__)

@app.after_request
def add_header(response):
    response.headers['X-Custom-Header'] = 'Hello'
    return response

Sample Program

This simple Flask app uses middleware to print the path of every request before showing the homepage.

Flask

from flask import Flask, request

app = Flask(__name__)

@app.before_request
def log_request():
    print(f"Request to {request.path}")

@app.route('/')
def home():
    return 'Welcome to the homepage!'

if __name__ == '__main__':
    app.run(debug=True)

Important Notes

Middleware runs for every request, so keep it fast and simple.

Use middleware to keep your main code clean and focused on core tasks.

Flask middleware can stop a request early by returning a response inside before_request.

Summary

Middleware adds extra steps before or after your main app code runs.

It helps with tasks like security, logging, and modifying requests or responses.

Using middleware keeps your app organized and easier to maintain.

Practice

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

easy

A. To add extra processing steps before or after the main app handles a request

B. To replace the Flask app's routing system

C. To directly modify the database schema

D. To serve static files like images and CSS

Solution

1. Step 1: Understand middleware role

   Middleware acts as a layer that processes requests or responses around the main app logic.

2. Step 2: Compare options

   Replacing routing, modifying database schema, or serving static files are not middleware tasks.

3. Final Answer:

   To add extra processing steps before or after the main app handles a request -> Option A

4. Quick Check:

   Middleware extends app functionality = C [OK]

Hint: Middleware adds steps around app requests and responses [OK]

Common Mistakes:

• Thinking middleware replaces routing
• Confusing middleware with static file serving
• Assuming middleware changes database structure

2. Which of the following is the correct way to add middleware in a Flask app?

easy

A. app = Middleware(app)

B. app.middleware = Middleware()

C. Middleware(app).run()

D. app.add_middleware(Middleware)

Solution

1. Step 1: Recall Flask middleware pattern

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

2. Step 2: Analyze options

   Only app = Middleware(app) correctly wraps the app instance. Others use invalid syntax or methods not in Flask.

3. Final Answer:

   app = Middleware(app) -> Option A

4. Quick Check:

   Middleware wraps app instance = A [OK]

Hint: Middleware wraps app like a gift box around it [OK]

Common Mistakes:

• Trying to assign middleware as an attribute
• Calling run() on middleware instead of app
• Using non-existent add_middleware method

3. Given this middleware code, 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 = SimpleMiddleware(app)

medium

A. No output printed

B. Only Before app printed

C. Only After app printed

D. Before app printed, then After app printed

Solution

1. Step 1: Understand __call__ method flow

   When a request comes, 'Before app' prints, then the wrapped app runs, then 'After app' prints.

2. Step 2: Confirm both prints execute

   Both print statements are before and after calling the app, so both appear in order.

3. Final Answer:

   Before app printed, then After app printed -> Option D

4. Quick Check:

   Middleware prints before and after app = A [OK]

Hint: Middleware prints before and after calling app [OK]

Common Mistakes:

• Thinking only one print runs
• Assuming prints happen in reverse order
• Forgetting __call__ runs on each request

4. This middleware code causes an error. What is the problem?

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 return a number, not a string

B. Middleware must call the wrapped app to return a valid response

C. Middleware should not have a __call__ method

D. Middleware __init__ method is missing

Solution

1. Step 1: Check __call__ method behavior

   The middleware returns a string directly without calling the wrapped app, breaking the request flow.

2. Step 2: Understand Flask middleware contract

   Middleware must call the wrapped app to get a valid response object, then return it.

3. Final Answer:

   Middleware must call the wrapped app to return a valid response -> Option B

4. Quick Check:

   Middleware must call app = D [OK]

Hint: Middleware must call wrapped app to work properly [OK]

Common Mistakes:

• Returning a string instead of calling app
• Missing __call__ method entirely
• Thinking middleware returns numbers

5. You want to add middleware that logs request paths and modifies the response to add a custom header. Which approach correctly extends functionality using middleware?

hard

A. Modify the Flask app routes to log and add headers directly inside each route function

B. Use middleware that only logs requests but does not call the app

C. Create middleware that logs environ['PATH_INFO'], calls the app, then adds header to response before returning

D. Add a middleware that replaces the response with a fixed string ignoring the app

Solution

1. Step 1: Understand middleware responsibilities

   Middleware should handle logging before calling the app and modify the response after.

2. Step 2: Evaluate options

   Create middleware that logs environ['PATH_INFO'], calls the app, then adds header to response before returning correctly logs the request path, calls the app, then modifies the response headers. Others either bypass app or do tasks incorrectly.

3. Final Answer:

   Create middleware that logs environ['PATH_INFO'], calls the app, then adds header to response before returning -> Option C

4. Quick Check:

   Middleware logs and modifies response = B [OK]

Hint: Middleware wraps app: log before, modify response after [OK]

Common Mistakes:

• Modifying routes instead of middleware
• Not calling the wrapped app
• Replacing response ignoring app output