Session handling in Ruby on Rails - Step-by-Step Execution

Concept Flow - Session handling

User sends HTTP request

↓

Rails receives request

↓

Check for session cookie

↓

Load session

↓

Controller action runs

↓

Modify session data?

↓

Send response with session cookie

↓

User browser stores cookie

Rails checks for a session cookie in the request. If found, it loads session data; if not, it creates a new session. Controller actions can read or write session data, then Rails sends a response with updated session info.

Execution Sample

Ruby on Rails

class ApplicationController < ActionController::Base
  def login
    session[:user_id] = params[:id]
    render plain: "Logged in as #{session[:user_id]}"
  end
end

This code saves a user ID in the session and shows a confirmation message.

Execution Table

Step	Request Detail	Session Cookie Present?	Session Data Before	Action	Session Data After	Response Sent
1	User sends login request with id=42	No	{}	Create new session, set session[:user_id] = 42	{user_id: 42}	Response with cookie and message 'Logged in as 42'
2	User sends another request with session cookie	Yes	{user_id: 42}	Read session[:user_id]	{user_id: 42}	Response with cookie and message 'Logged in as 42'
3	User sends logout request clearing session	Yes	{user_id: 42}	Clear session data	{}	Response with cleared cookie

💡 Session ends when user logs out or session expires, no session cookie sent.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3
session[:user_id]	nil	42	42	nil

Key Moments - 3 Insights

Why does the session data persist between requests?

Because Rails sends a session cookie to the browser in the response (see Step 1), which the browser sends back in the next request (Step 2), allowing Rails to load the saved session data.

What happens if the user has no session cookie?

Rails creates a new empty session (Step 1), so session data starts fresh. This is shown in the first row where session is empty before setting user_id.

How does Rails clear session data on logout?

The controller action clears session data (Step 3), and Rails sends a response that instructs the browser to remove the session cookie, ending the session.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of session[:user_id] after Step 1?

A {}

B nil

C 42

D undefined

💡 Hint

Check the 'Session Data After' column in Step 1.

At which step does Rails create a new session because no cookie is present?

A Step 2

B Step 1

C Step 3

D None

💡 Hint

Look at the 'Session Cookie Present?' column and find where it says 'No'.

If the user clears cookies manually, what will happen on the next request?

A Rails will create a new session

B Rails will load old session data

C Rails will throw an error

D Session data will be unchanged

💡 Hint

Refer to the flow where no session cookie means a new session is created.

Concept Snapshot

Session handling in Rails:
- Rails uses cookies to track sessions.
- On request, Rails checks for session cookie.
- If none, creates new session.
- Controller can read/write session[:key].
- Response sends updated cookie.
- Session persists across requests via cookie.

Full Transcript

In Rails, session handling works by using cookies to remember user data between requests. When a user sends a request, Rails looks for a session cookie. If it finds one, it loads the saved session data. If not, it creates a new session. Controller actions can store or read data in the session hash, like session[:user_id]. After processing, Rails sends a response that includes the session cookie so the browser can keep it. This way, the session data persists across multiple requests. When the user logs out, the session data is cleared and the cookie is removed, ending the session.

Practice

1. What is the main purpose of using session in a Rails application?

easy

A. To style the webpage dynamically

B. To handle file uploads

C. To connect to the database

D. To store user data across multiple requests

Solution

1. Step 1: Understand what sessions do

   Sessions keep data between different pages or requests for the same user.

2. Step 2: Identify the correct purpose

   Storing user data like login status or preferences is the main use of sessions.

3. Final Answer:

   To store user data across multiple requests -> Option D

4. Quick Check:

   Sessions remember user info across pages = B [OK]

Hint: Sessions keep user info between pages [OK]

Common Mistakes:

• Confusing sessions with styling or database connections
• Thinking sessions handle file uploads

2. Which of the following is the correct way to store a user's name in the session in Rails?

easy

A. session = { name: 'Alice' }

B. session[:name] = 'Alice'

C. session.name = 'Alice'

D. session('name') = 'Alice'

Solution

1. Step 1: Recall session syntax in Rails

   Sessions use a hash-like syntax with square brackets and symbols for keys.

2. Step 2: Match the correct syntax

   Assigning with session[:name] = 'Alice' is the proper way.

3. Final Answer:

   session[:name] = 'Alice' -> Option B

4. Quick Check:

   Use session[:key] = value syntax = A [OK]

Hint: Use session[:key] = value to store data [OK]

Common Mistakes:

• Using assignment with equals on session itself
• Trying to call session like a method
• Using dot notation which is invalid

3. What will be the output of the following Rails controller code snippet?

session[:count] ||= 0
session[:count] += 1
render plain: session[:count]

medium

A. nil

B. 0

C. 1

D. Error

Solution

1. Step 1: Understand the ||= operator

   If session[:count] is nil or false, it sets it to 0; otherwise, it keeps the value.

2. Step 2: Increment the count

   After setting to 0 if needed, it adds 1, so the value becomes 1.

3. Final Answer:

   1 -> Option C

4. Quick Check:

   Initialize or keep count, then add 1 = 1 [OK]

Hint: ||= sets default, then += increments [OK]

Common Mistakes:

• Thinking ||= 0 sets count to 0 every time
• Expecting output 0 instead of 1
• Assuming session[:count] is nil after increment

4. Identify the error in this Rails controller code that tries to clear the session:

def logout
  session.clear()
  redirect_to root_path
end

medium

A. No error; code correctly clears the session

B. Missing parentheses in session.clear call

C. session.clear should be session.delete_all

D. session.clear is not a valid method

Solution

1. Step 1: Check session clearing methods in Rails

   Rails session supports clear method to remove all keys.

2. Step 2: Verify syntax and usage

   Calling session.clear() is valid and clears the session.

3. Final Answer:

   No error; code correctly clears the session -> Option A

4. Quick Check:

   session.clear() clears session correctly = D [OK]

Hint: session.clear() empties session data correctly [OK]

Common Mistakes:

• Thinking session.clear() is invalid
• Confusing with database delete methods
• Assuming parentheses are mandatory or cause error

5. You want to store a user's preferred language in the session only if it is not already set. Which code snippet correctly does this in a Rails controller?

hard

A. All of the above

B. session[:language] ||= params[:language]

C. session[:language] = params[:language] if session[:language].nil?

D. session[:language] = params[:language] unless session[:language]

Solution

1. Step 1: Understand the goal

   We want to set session[:language] only if it is not already set.

2. Step 2: Analyze each option

   session[:language] = params[:language] if session[:language].nil? uses if session[:language].nil?, which sets only if nil.
   session[:language] ||= params[:language] uses ||= which sets if false or nil.
   session[:language] = params[:language] unless session[:language] uses unless session[:language], which sets if false or nil.
   All three effectively do the same thing.

3. Final Answer:

   All of the above -> Option A

4. Quick Check:

   All three set only if session[:language] is unset = C [OK]

Hint: ||= or conditional assignment both work [OK]

Common Mistakes:

• Thinking only ||= works
• Confusing unless with if
• Setting session unconditionally