Session handling in Ruby on Rails - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a session in Rails?

A session in Rails is a way to store data about a user across multiple requests. It helps keep track of user information like login status while they browse the site.

beginner

How does Rails store session data by default?

By default, Rails stores session data in a cookie on the user's browser. This cookie is encrypted and signed to keep data safe and prevent tampering.

beginner

How do you set a value in the session in a Rails controller?

You set a session value by assigning it like a hash:
session[:user_id] = 123 This saves the user ID in the session for later use.

intermediate

What is the difference between session and cookies in Rails?

Cookies store data directly on the browser and can be read by client-side scripts. Sessions store data encrypted and signed in cookies and are used to keep user state securely across requests.

beginner

How can you clear all session data in Rails?

You can clear all session data by calling reset_session in a controller. This removes all stored session information for the user.

Where is session data stored by default in Rails?

A In an encrypted cookie on the browser

B In the database automatically

C In a server-side file

D In localStorage

Rails stores session data in an encrypted cookie on the user's browser by default.

How do you access session data in a Rails controller?

A Using request[:key]

B Using params[:key]

C Using cookies[:key]

D Using the session hash, like session[:key]

Session data is accessed via the session hash, for example session[:user_id].

What method clears all session data in Rails?

A delete_session

B clear_session

C reset_session

D remove_session

The reset_session method clears all session data for the current user.

Which of these is true about Rails sessions?

A Session data can be encrypted and signed in cookies

B Session data is visible to client-side JavaScript by default

C Session data is always stored on the server

D Sessions cannot store user login information

Rails encrypts and signs session data stored in cookies to keep it secure.

What is a common use of sessions in Rails apps?

A To permanently save user data in the database

B To store temporary user login status

C To style the webpage dynamically

D To send emails to users

Sessions commonly store temporary data like user login status during browsing.

Explain how Rails sessions help keep track of a user across multiple pages.

Think about how a website remembers you after you log in.

Describe how to set, access, and clear session data in a Rails controller.

Focus on the session hash and controller methods.

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