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.

Practice

1. What is the main purpose of using session data storage in a Flask web application?

easy

A. To permanently save data on the server's hard drive

B. To keep user information between different pages securely

C. To speed up the loading of static files like images

D. To replace cookies with a faster alternative

Solution

1. Step 1: Understand session data role

   Session data stores user info temporarily during their visit to keep state across pages.

2. Step 2: Differentiate from other storage

   It is not permanent storage or related to static files; it keeps data safe between requests.

3. Final Answer:

   To keep user information between different pages securely -> Option B

4. Quick Check:

   Session stores user info between pages = A [OK]

Hint: Sessions keep user info across pages safely [OK]

Common Mistakes:

• Confusing session with permanent database storage
• Thinking session speeds up static file loading
• Believing session replaces cookies entirely

2. Which line of code correctly sets the secret key needed for Flask sessions?

easy

A. app.set_secret('mysecret')

B. session.secret = 'mysecret'

C. app.secret_key = 'mysecret'

D. app.session_key = 'mysecret'

Solution

1. Step 1: Recall Flask session setup

   Flask requires setting app.secret_key to enable session encryption.

2. Step 2: Check syntax correctness

   Only app.secret_key = 'mysecret' is valid; others are invalid method or attribute names.

3. Final Answer:

   app.secret_key = 'mysecret' -> Option C

4. Quick Check:

   Set secret_key with app.secret_key = value [OK]

Hint: Use app.secret_key to enable sessions [OK]

Common Mistakes:

• Using wrong attribute like app.session_key
• Trying to call a non-existent method set_secret
• Assigning secret to session object instead of app

3. Given this Flask code snippet:

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

@app.route('/')
def index():
    session['count'] = session.get('count', 0) + 1
    return str(session['count'])

What will the user see on their first visit to the '/' route?

medium

A. 0

B. Error

C. None

D. 1

Solution

1. Step 1: Analyze session count initialization

   On first visit, session.get('count', 0) returns 0, then adds 1, so count becomes 1.

2. Step 2: Understand return value

   The function returns the string of session['count'], which is '1'.

3. Final Answer:

   1 -> Option D

4. Quick Check:

   First visit count = 1 [OK]

Hint: session.get with default 0 then add 1 means first count is 1 [OK]

Common Mistakes:

• Thinking count starts at 0 instead of 1
• Expecting None because key is missing
• Assuming code causes an error without secret_key

4. What is wrong with this Flask code snippet for storing session data?

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

@app.route('/')
def index():
    session['user'] = 'Alice'
    return session['user']

medium

A. Missing app.secret_key setup

B. session['user'] cannot store strings

C. Flask app must import request to use session

D. Route decorator syntax is incorrect

Solution

1. Step 1: Check session requirements

   Flask sessions require app.secret_key to be set for security.

2. Step 2: Identify missing secret_key

   The code does not set app.secret_key, so session will not work properly.

3. Final Answer:

   Missing app.secret_key setup -> Option A

4. Quick Check:

   Sessions need app.secret_key set [OK]

Hint: Always set app.secret_key before using session [OK]

Common Mistakes:

• Thinking session can't store strings
• Believing request import is needed for session
• Assuming route decorator syntax is wrong

5. You want to store a user's preferred language in the session and retrieve it safely. Which code snippet correctly sets and reads this value in Flask?

hard

A. session['lang'] = 'en'
language = session.get('lang', 'default')

B. session.set('lang', 'en')
language = session.get('lang')

C. session['lang'] = 'en'
language = session['lang']

D. session['lang'] = 'en'
language = session['language']

Solution

1. Step 1: Correctly set session key

   Assigning with session['lang'] = 'en' is correct to store the language.

2. Step 2: Safely retrieve session value

   Using session.get('lang', 'default') safely reads the value with a fallback if missing.

3. Final Answer:

   session['lang'] = 'en'\nlanguage = session.get('lang', 'default') -> Option A

4. Quick Check:

   Use session.get to safely read session keys [OK]

Hint: Use session.get('key', default) to avoid errors [OK]

Common Mistakes:

• Using session.set which does not exist
• Accessing wrong key name on read
• Not providing default causing KeyError