Session data storage in Flask - Step-by-Step Execution

Concept Flow - Session data storage

User sends request

↓

Flask checks session cookie

↓

Load session data from cookie or server

↓

Access or modify session data

↓

Send response with updated session cookie

↓

User browser stores updated cookie

↓

Next request uses updated session data

This flow shows how Flask reads, updates, and saves session data using cookies between user requests.

Execution Sample

Flask

from flask import Flask, session
app = Flask(__name__)
app.secret_key = 'secret'

@app.route('/')
def index():
    session['count'] = session.get('count', 0) + 1
    return f"Count: {session['count']}"

This code counts how many times a user visits the page by storing a number in the session.

Execution Table

Step	Request Number	Session Before	Action	Session After	Response Output
1	1	{}	session.get('count', 0) + 1 = 1	{'count': 1}	Count: 1
2	2	{'count': 1}	session.get('count', 0) + 1 = 2	{'count': 2}	Count: 2
3	3	{'count': 2}	session.get('count', 0) + 1 = 3	{'count': 3}	Count: 3
4	4	{'count': 3}	session.get('count', 0) + 1 = 4	{'count': 4}	Count: 4
5	5	{'count': 4}	session.get('count', 0) + 1 = 5	{'count': 5}	Count: 5
6	6	{'count': 5}	session.get('count', 0) + 1 = 6	{'count': 6}	Count: 6
Exit	7	{'count': 6}	Stop after 6 requests	{'count': 6}	Session persists until cleared or expired

💡 Session count increments with each request until stopped or session expires.

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5	After 6	Final
session['count']	undefined	1	2	3	4	5	6	6

Key Moments - 3 Insights

Why does session['count'] start as undefined on the first request?

Because the session cookie is empty on the first request, so session.get('count', 0) returns 0, then adds 1 to store 1.

How does Flask remember session data between requests?

Flask stores session data in a cookie sent to the browser, which is sent back with each request, allowing Flask to load previous session data.

What happens if the secret_key is not set?

Flask cannot securely sign the session cookie, so session data storage will fail or raise an error.

Visual Quiz - 3 Questions

Look at the execution table, what is session['count'] at step 3?

A 2

B 3

C 1

D undefined

💡 Hint

Check the 'Session After' column at step 3 in the execution table.

At which request number does the session count become 5?

A 5

B 4

C 6

D 3

💡 Hint

Look at the 'Session After' column and find when 'count' equals 5.

If the secret_key is missing, what will happen to the session data?

A Session data will be stored normally

B Session data will reset to zero automatically

C Session data will not be saved securely and may cause errors

D Session data will be stored on the server only

💡 Hint

Refer to the key moment about secret_key importance.

Concept Snapshot

Flask session stores data per user using cookies.
Set app.secret_key to secure session data.
Access session like a dictionary: session['key'] = value.
Data persists across requests until cleared or expired.
Session data is signed and stored client-side by default.

Full Transcript

This session data storage example in Flask shows how the app uses a secret key to sign session cookies. Each user request sends the cookie back, allowing Flask to load and update session data. The example increments a count stored in session on each visit. The execution table traces six requests, showing the count increasing from 1 to 6. The variable tracker highlights session['count'] changes. Key moments clarify why the count starts undefined, how Flask remembers session data, and the importance of secret_key. The visual quiz tests understanding of session values at specific steps and the role of secret_key. This helps beginners see how session data flows and persists in Flask apps.