Request context in Flask - Step-by-Step Execution

Concept Flow - Request context

Start HTTP Request

↓

Create Request Context

↓

Push Context to stack

↓

Handle Request in View

↓

Access request, session, g

↓

Return Response

↓

Pop Context from stack

↓

End HTTP Request

Flask creates a request context for each HTTP request, pushes it to a stack, lets the view access request data, then pops it after response.

Execution Sample

Flask

from flask import Flask, request
app = Flask(__name__)

@app.route('/')
def home():
    return f"You requested {request.path}"

This code creates a Flask app that returns the path of the current request using the request context.

Execution Table

Step	Action	Request Context State	Accessed Variables	Output
1	Start HTTP request to '/'	No context yet	null	null
2	Create request context for '/'	Context created with path='/'	null	null
3	Push context to stack	Context active on stack	null	null
4	Call view function 'home'	Context active	request.path='/'	null
5	Return response string	Context active	request.path='/'	You requested /
6	Pop context from stack	Context removed	null	null
7	End HTTP request	No context	null	Response sent

💡 Request ends after response sent and context popped from stack

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 6	Final
request.path	null	null	/	/	null	null
request context stack	Empty	Empty	Contains context	Contains context	Empty	Empty

Key Moments - 2 Insights

Why can we access 'request.path' inside the view without passing it explicitly?

Because Flask pushes a request context on a stack before calling the view (see execution_table step 3), making 'request' available globally during the request.

What happens if we try to access 'request' outside a request context?

There is no active request context (see execution_table step 1 or 7), so accessing 'request' will raise an error because Flask doesn't know which request you mean.

Visual Quiz - 3 Questions

Look at the execution table, at which step is the request context pushed to the stack?

A Step 3

B Step 2

C Step 4

D Step 6

💡 Hint

Check the 'Action' and 'Request Context State' columns around steps 2-4.

According to the variable tracker, what is the value of 'request.path' after step 4?

A null

B '/home'

C '/'

D Empty string

💡 Hint

Look at the 'request.path' row under 'After Step 4' column.

If the context was not popped at step 6, what would happen?

A The response would not be sent.

B The request context stack would remain full, possibly causing memory issues.

C The view function would not run.

D The request path would change.

💡 Hint

Refer to the 'request context stack' row in variable_tracker after step 6.

Concept Snapshot

Flask creates a request context for each HTTP request.
This context is pushed to a stack before the view runs.
Inside the view, 'request' and other globals are accessible.
After the response, the context is popped from the stack.
Accessing 'request' outside this context causes errors.

Full Transcript

When Flask receives an HTTP request, it creates a request context that holds data about the request, like the URL path. This context is pushed onto a stack so that inside the view function, you can access 'request' and other related objects without passing them explicitly. After the view returns a response, Flask pops the context off the stack to clean up. If you try to use 'request' outside this context, Flask will raise an error because it doesn't know which request you mean. This flow ensures each request is handled separately and safely.