WSGI middleware concept in Flask - Step-by-Step Execution

Concept Flow - WSGI middleware concept

Client Request

↓

WSGI Server

↓

Middleware: Receives Request

↓

Middleware: Processes or Modifies Request

↓

Passes Request to Flask App

↓

Flask App: Generates Response

↓

Middleware: Receives Response

↓

Middleware: Processes or Modifies Response

↓

WSGI Server

↓

Client Receives Response

The WSGI middleware sits between the server and the Flask app, intercepting requests and responses to modify or process them before passing along.

Execution Sample

Flask

def simple_middleware(app):
    def middleware(environ, start_response):
        print('Before app')
        response = app(environ, start_response)
        print('After app')
        return response
    return middleware

This middleware prints messages before and after calling the Flask app, showing how it wraps the app call.

Execution Table

Step	Action	Evaluation	Result
1	Client sends request	Request data created	Request ready for server
2	WSGI server receives request	Prepares environ dict	Environ passed to middleware
3	Middleware receives request	Prints 'Before app'	Logs message before app call
4	Middleware calls Flask app	Flask app processes request	Response generated
5	Middleware receives response	Prints 'After app'	Logs message after app call
6	Middleware returns response	Response passed to server	Server sends response to client
7	Client receives response	Response displayed	Request cycle complete

💡 Request cycle ends after response is sent back to client

Variable Tracker

Variable	Start	After Step 3	After Step 4	After Step 5	Final
environ	None	Request data dict	Passed to app	Passed back from app	Used by server
response	None	None	Flask app response	Middleware response	Sent to client

Key Moments - 3 Insights

Why does the middleware print 'Before app' before calling the Flask app?

Because middleware runs code before passing the request to the app, as shown in step 3 of the execution_table.

How does the middleware modify the response after the Flask app processes the request?

Middleware can run code after the app call, like printing 'After app' in step 5, allowing it to change or log the response.

What is the role of the 'environ' variable in the middleware?

'environ' holds request data passed from server to middleware and then to the Flask app, tracked in variable_tracker.

Visual Quiz - 3 Questions

Look at the execution_table, what is printed by the middleware before calling the Flask app?

A 'After app'

B 'Before app'

C 'Request received'

D 'Response sent'

💡 Hint

Check step 3 in the execution_table where middleware prints before calling the app.

At which step does the Flask app generate the response?

A Step 3

B Step 5

C Step 4

D Step 6

💡 Hint

Look at step 4 in the execution_table where the app processes the request.

If the middleware did not call the Flask app, what would happen to the response variable?

A It would be None and no response sent

B It would contain the request data

C It would be the final response

D It would cause an error in the server

💡 Hint

Refer to variable_tracker and execution_table steps 3 and 4 about response assignment.

Concept Snapshot

WSGI middleware wraps the Flask app call.
It receives the request environ and can modify it.
Calls the app to get a response.
Can modify the response before returning.
Acts as a bridge between server and app.
Useful for logging, auth, or modifying requests/responses.

Full Transcript

WSGI middleware is a piece of code that sits between the WSGI server and the Flask application. When a client sends a request, the server passes it to the middleware first. The middleware can look at or change the request before sending it to the Flask app. After the Flask app creates a response, the middleware can again modify or log the response before sending it back to the server, which then sends it to the client. This process allows middleware to add features like logging or authentication without changing the Flask app itself. The example code shows middleware printing messages before and after calling the app, demonstrating how it wraps the app call. Variables like 'environ' hold request data and 'response' holds the app's output, both tracked through the steps. Understanding this flow helps beginners see how middleware fits into the request-response cycle.