Session framework configuration in Django - Step-by-Step Execution

Concept Flow - Session framework configuration

Start Django Project

↓

Add 'django.contrib.sessions' to INSTALLED_APPS

↓

Configure SESSION_ENGINE in settings.py

↓

Run migrations to create session tables

↓

Use session in views to store/retrieve data

↓

Session data saved and retrieved per user

↓

End

This flow shows how Django session framework is set up and used step-by-step.

Execution Sample

Django

INSTALLED_APPS = [
    'django.contrib.sessions',
    # other apps
]

SESSION_ENGINE = 'django.contrib.sessions.backends.db'

# In a view:
request.session['key'] = 'value'

This code configures Django to use database-backed sessions and stores a value in the session.

Execution Table

Step	Action	Settings State	Effect	Session Data
1	Add 'django.contrib.sessions' to INSTALLED_APPS	INSTALLED_APPS includes sessions	Enables session app	{}
2	Set SESSION_ENGINE to 'django.contrib.sessions.backends.db'	SESSION_ENGINE set	Use DB for session storage	{}
3	Run migrations	Session tables created	DB ready for sessions	{}
4	In view, assign request.session['key'] = 'value'	Session engine active	Stores 'key':'value' in session	{"key": "value"}
5	Retrieve request.session['key']	Session engine active	Returns 'value'	{"key": "value"}
6	Session persists per user across requests	Session engine active	Data available until expiry or clear	{"key": "value"}
7	Session expires or cleared	Session engine active	Session data removed	{}

💡 Session data lifecycle ends when session expires or is cleared

Variable Tracker

Variable	Start	After Step 4	After Step 5	After Step 6	After Step 7
INSTALLED_APPS	Does not include sessions	Includes sessions	Includes sessions	Includes sessions	Includes sessions
SESSION_ENGINE	Not set	Set to DB backend	Set to DB backend	Set to DB backend	Set to DB backend
Session Data	{}	{"key": "value"}	{"key": "value"}	{"key": "value"}	{}

Key Moments - 3 Insights

Why do we need to add 'django.contrib.sessions' to INSTALLED_APPS?

Because Django only activates session features if the sessions app is listed in INSTALLED_APPS, as shown in step 1 of the execution_table.

What does setting SESSION_ENGINE to 'django.contrib.sessions.backends.db' do?

It tells Django to store session data in the database, enabling persistence across requests, as seen in step 2 and 3.

How does session data persist across user requests?

Session data is saved in the backend (database here) and linked to the user via a cookie, so data like {'key': 'value'} remains available until expiry or clearing, shown in steps 4 to 6.

Visual Quiz - 3 Questions

Look at the execution_table, what is the session data after step 4?

A {}

B {"user": "admin"}

C {"key": "value"}

D null

💡 Hint

Check the 'Session Data' column at step 4 in the execution_table.

At which step does Django create the database tables for sessions?

A Step 2

B Step 3

C Step 5

D Step 1

💡 Hint

Look for the step mentioning migrations and DB readiness in the execution_table.

If SESSION_ENGINE was not set, what would happen to session data?

A Session data would be stored in the database anyway

B Session data would be stored in cookies by default

C Session data would not persist across requests

D Session data would be lost immediately

💡 Hint

Django's default SESSION_ENGINE is 'django.contrib.sessions.backends.db'.

Concept Snapshot

Django session framework stores user data across requests.
Add 'django.contrib.sessions' to INSTALLED_APPS.
Set SESSION_ENGINE to choose storage (DB, cache, cookies).
Run migrations to create session tables if using DB.
Use request.session dict in views to save/retrieve data.
Session persists until expiry or manual clearing.

Full Transcript

This visual execution trace shows how to configure Django's session framework. First, you add 'django.contrib.sessions' to INSTALLED_APPS to enable session support. Then, you set SESSION_ENGINE in settings.py to specify where session data is stored; here, the database backend is used. Running migrations creates the necessary database tables. In views, you can store data in request.session like a dictionary. This data persists across user requests until the session expires or is cleared. The execution table tracks these steps and session data changes. Key points include the need to add the sessions app, the role of SESSION_ENGINE, and how session data persists. The quiz tests understanding of these steps and session behavior.

Practice

1. What is the main purpose of Django's session framework?

easy

A. To store static files like images and CSS

B. To handle database migrations automatically

C. To remember user data between different pages

D. To manage user authentication only

Solution

1. Step 1: Understand session framework role

   Django sessions store data to keep track of users as they move between pages.

2. Step 2: Compare options with session purpose

   Only To remember user data between different pages describes remembering user data between pages, which is the session's job.

3. Final Answer:

   To remember user data between different pages -> Option C

4. Quick Check:

   Sessions remember users = B [OK]

Hint: Sessions remember users across pages, not files or migrations [OK]

Common Mistakes:

• Confusing sessions with static file storage
• Thinking sessions only handle login
• Mixing sessions with database migrations

2. Which setting in settings.py specifies the backend storage for sessions?

easy

A. SESSION_ENGINE

B. SESSION_COOKIE_AGE

C. SESSION_SAVE_EVERY_REQUEST

D. SESSION_EXPIRE_AT_BROWSER_CLOSE

Solution

1. Step 1: Identify session backend setting

   The setting that controls where sessions are stored is SESSION_ENGINE.

2. Step 2: Review other options

   Other options control cookie age, saving behavior, or expiration, not storage backend.

3. Final Answer:

   SESSION_ENGINE -> Option A

4. Quick Check:

   Backend storage = SESSION_ENGINE [OK]

Hint: SESSION_ENGINE sets storage backend, not cookie or expiration [OK]

Common Mistakes:

• Confusing SESSION_ENGINE with cookie age
• Mixing save behavior with storage backend
• Assuming expiration settings control storage

3. Given this settings.py snippet:

SESSION_ENGINE = 'django.contrib.sessions.backends.cache'
SESSION_COOKIE_AGE = 1209600  # 2 weeks
SESSION_EXPIRE_AT_BROWSER_CLOSE = False

What happens when a user closes and reopens their browser?

medium

A. The session cookie is deleted but data remains in cache

B. The session expires immediately on browser close

C. The session is stored in the database and expires on logout

D. The session is kept for 2 weeks and user stays logged in

Solution

1. Step 1: Analyze SESSION_EXPIRE_AT_BROWSER_CLOSE

   It is set to False, so session cookies do not expire when browser closes.

2. Step 2: Check SESSION_COOKIE_AGE

   Set to 2 weeks, so session lasts that long unless user logs out.

3. Final Answer:

   The session is kept for 2 weeks and user stays logged in -> Option D

4. Quick Check:

   Expire at close = False means session kept [OK]

Hint: False expire at close means session lasts cookie age [OK]

Common Mistakes:

• Assuming session expires on browser close by default
• Confusing cache backend with database storage
• Thinking cookie deletion removes session data immediately

4. You set SESSION_ENGINE = 'django.contrib.sessions.backends.file' but get errors about missing directories. What is the likely cause?

medium

A. The session file directory does not exist or lacks write permission

B. SESSION_ENGINE value is invalid and causes syntax error

C. You forgot to add sessions to INSTALLED_APPS

D. SESSION_COOKIE_AGE is set too low causing session loss

Solution

1. Step 1: Understand file backend requirements

   The file backend stores sessions in files, needing a writable directory.

2. Step 2: Identify cause of errors

   If directory is missing or not writable, errors occur when saving sessions.

3. Final Answer:

   The session file directory does not exist or lacks write permission -> Option A

4. Quick Check:

   File backend needs writable directory [OK]

Hint: File backend needs writable folder, else errors occur [OK]

Common Mistakes:

• Assuming SESSION_ENGINE value syntax is wrong
• Forgetting sessions are built-in, no INSTALLED_APPS needed
• Blaming cookie age for file write errors

5. You want sessions to expire when the user closes the browser but also want to keep sessions for 1 hour if the browser stays open. Which settings combination achieves this?

hard

A. SESSION_EXPIRE_AT_BROWSER_CLOSE = False and SESSION_COOKIE_AGE = 3600

B. SESSION_EXPIRE_AT_BROWSER_CLOSE = True and SESSION_COOKIE_AGE = 3600

C. SESSION_EXPIRE_AT_BROWSER_CLOSE = True and SESSION_COOKIE_AGE = None

D. SESSION_EXPIRE_AT_BROWSER_CLOSE = False and SESSION_COOKIE_AGE = None

Solution

1. Step 1: Understand SESSION_EXPIRE_AT_BROWSER_CLOSE

   Setting it to True makes the session expire when browser closes.

2. Step 2: Understand SESSION_COOKIE_AGE

   Setting it to 3600 seconds (1 hour) limits session lifetime if browser stays open.

3. Final Answer:

   SESSION_EXPIRE_AT_BROWSER_CLOSE = True and SESSION_COOKIE_AGE = 3600 -> Option B

4. Quick Check:

   Expire at close True + 1 hour age = A [OK]

Hint: Expire at close True + cookie age limits session time [OK]

Common Mistakes:

• Setting expire at close False when wanting session to end on close
• Using None for cookie age disables expiration
• Confusing cookie age with session storage backend