Request Lifecycle & Context
Understand app and request contexts and g.
Recipe
Quick-reference recipe card - copy-paste ready.
from flask import Flask, g, request
app = Flask(__name__)
@app.before_request
def load_user():
g.user = request.headers.get("X-User")When to reach for this:
- Per-request state in
g - before_request hooks
- teardown handlers
Working Example
from flask import Flask, g
app = Flask(__name__)
@app.teardown_request
def teardown(exc):
g.pop("user", None)What this demonstrates:
- teardown_request
- g cleanup
- context locals
Deep Dive
How It Works
- Request context pushes per HTTP request.
- App context needed for
current_appoutside requests. - Do not share mutable globals across threads.
Gotchas
- Boundary validation skipped - Invalid data reaches persistence layers.. Fix: Validate with Pydantic or framework forms at the edge..
- Leaking stack traces - Clients see internal errors.. Fix: Map exceptions to stable HTTP responses..
- Blocking async event loops - Workers stall under concurrent load.. Fix: Use async drivers or threadpool wrappers..
- Secrets in source control - Credentials leak via git history.. Fix: Load secrets from env or a vault at runtime..
- Missing observability - Incidents are hard to debug.. Fix: Add structured logs, metrics, and request IDs..
Alternatives
| Alternative | Use When | Don't Use When |
|---|---|---|
| Alternate framework in this cookbook | Team standard or existing monolith | Greenfield API with different constraints |
| Managed BaaS | CRUD-only MVP | Custom auth, workflows, or compliance needs |
| gRPC | Internal high-performance RPC | Public HTTP clients and browser access |
FAQs
When should I adopt Flask context?
Use it when the patterns and trade-offs on this page match your API or data boundary.
What is the top production mistake with Flask context?
Skipping validation, timeouts, or explicit error contracts at the HTTP edge.
How do I test Flask context?
Use the framework test client, override dependencies, and assert status plus JSON shape.
Does Flask context work with Python 3.14?
Yes - examples target Python 3.14 with pinned framework versions from the stack footer.
How does Flask context relate to Pydantic 2?
Validate and serialize at boundaries; keep services working with typed domain objects.
Sync or async?
Prefer async routes when I/O dominates; keep CPU work small or offload to workers.
Where should business logic live?
Thin handlers; services own rules; repositories own queries.
How do I document APIs?
Publish OpenAPI or schema docs that match response models in code.
How do I handle versioning?
Explicit URL or header versioning with deprecation windows - avoid silent breaks.
What should I read next?
Follow the Related links for the next layer of depth in this section.
How do I stay secure?
Authenticate callers, authorize per resource, rate-limit, and never log secrets.
Performance first step?
Measure DB and upstream latency before swapping frameworks.
Related
- Flask Basics - Routes and requests
- Application Factories & Blueprints - Structure
- Building REST APIs - JSON endpoints
- Deploying Flask - WSGI production
Stack versions: This page was written for Python 3.14.0 (stable 3.14, maintenance 3.13), FastAPI 0.115+, Django 5.2, Flask 3.1, Pydantic 2, PyTorch 2.6+, pandas 2.2+, Polars 1.x, ruff 0.9+, and uv 0.6+.