Cookie session storage in Remix - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a cookie session storage using Remix.

Remix

import { createCookieSessionStorage } from '@remix-run/node';

const sessionStorage = createCookieSessionStorage({
  cookie: {
    name: '[1]',
    secrets: ['s3cret'],
    sameSite: 'lax',
  },
});

Drag options to blanks, or click blank then click option'

Acookie_data

Bsession_id

Cauth_token

Duser_session

Attempts:

3 left

💡 Hint

Common Mistakes

Using a name that is too generic or unrelated to sessions.

Leaving the name empty or undefined.

The name property defines the cookie's name. session_id is a common and clear choice for session cookies.

2fill in blank

medium

Complete the code to get the session from the request using the session storage.

Remix

export async function loader({ request }) {
  const session = await sessionStorage.[1](request.headers.get('Cookie'));
  return new Response('OK');
}

Drag options to blanks, or click blank then click option'

AreadSession

BloadSession

CfetchSession

DgetSession

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent methods like 'loadSession' or 'fetchSession'.

Trying to access session directly without calling a method.

The getSession method retrieves the session from the cookie header.

3fill in blank

hard

Fix the error in setting a value in the session and committing it to the response headers.

Remix

export async function action({ request }) {
  const session = await sessionStorage.getSession(request.headers.get('Cookie'));
  session.[1]('userId', '123');
  return new Response('Logged in', {
    headers: {
      'Set-Cookie': await sessionStorage.commitSession(session),
    },
  });
}

Drag options to blanks, or click blank then click option'

Aset

Badd

Cupdate

Dput

Attempts:

3 left

💡 Hint

Common Mistakes

Using methods like 'add' or 'put' which do not exist on the session object.

Trying to assign values directly without using a method.

The set method is used to add or update a value in the session.

4fill in blank

hard

Fill both blanks to create a session and destroy it in the response.

Remix

export async function logout({ request }) {
  const session = await sessionStorage.[1](request.headers.get('Cookie'));
  return new Response('Logged out', {
    headers: {
      'Set-Cookie': await sessionStorage.[2](session),
    },
  });
}

Drag options to blanks, or click blank then click option'

AgetSession

BdestroySession

CcommitSession

DloadSession

Attempts:

3 left

💡 Hint

Common Mistakes

Using commitSession instead of destroySession to clear the cookie.

Trying to destroy the session before getting it.

First, get the session with getSession. Then destroy it with destroySession to clear the cookie.

5fill in blank

hard

Fill all three blanks to create a session, set a value, and commit it in the response.

Remix

export async function login({ request }) {
  const session = await sessionStorage.[1](request.headers.get('Cookie'));
  session.[2]('username', 'alice');
  return new Response('Welcome', {
    headers: {
      'Set-Cookie': await sessionStorage.[3](session),
    },
  });
}

Drag options to blanks, or click blank then click option'

AgetSession

Bset

CcommitSession

DdestroySession

Attempts:

3 left

💡 Hint

Common Mistakes

Using destroySession instead of commitSession.

Trying to set values before getting the session.

Use getSession to get the session, set to add data, and commitSession to save it in the cookie.

Practice

1. What is the main purpose of using cookie session storage in Remix Framework?

easy

A. To keep user data between page visits using browser cookies

B. To store large files on the server

C. To speed up database queries

D. To change the website's layout dynamically

Solution

1. Step 1: Understand cookie session storage role

   Cookie session storage saves small pieces of user data in browser cookies to remember users across visits.

2. Step 2: Identify correct purpose in Remix

   Remix uses cookie sessions to keep user info safely between page loads, not for server files or layout changes.

3. Final Answer:

   To keep user data between page visits using browser cookies -> Option A

4. Quick Check:

   Cookie session storage = keep user data [OK]

Hint: Remember: cookie sessions store user info in browser cookies [OK]

Common Mistakes:

• Confusing cookie storage with server file storage
• Thinking cookie sessions speed up database queries
• Assuming cookie sessions change page layout

2. Which of the following is the correct way to create a cookie session in Remix?

easy

A. import { cookieSession } from 'remix-framework';

B. import { createSessionCookie } from 'remix';

C. import { sessionCookieCreate } from '@remix-run/server';

D. import { createCookieSessionStorage } from '@remix-run/node';

Solution

1. Step 1: Recall Remix cookie session import syntax

   Remix uses createCookieSessionStorage from '@remix-run/node' to handle cookie sessions.

2. Step 2: Compare options to correct import

   Only import { createCookieSessionStorage } from '@remix-run/node'; matches the official Remix import statement exactly.

3. Final Answer:

   import { createCookieSessionStorage } from '@remix-run/node'; -> Option D

4. Quick Check:

   Correct import = import { createCookieSessionStorage } from '@remix-run/node'; [OK]

Hint: Look for '@remix-run/node' and 'createCookieSessionStorage' keywords [OK]

Common Mistakes:

• Using wrong package names like 'remix-framework'
• Mixing function names like 'createSessionCookie'
• Importing from '@remix-run/server' instead of '@remix-run/node'

3. Given this Remix code snippet, what will be the value of userId after reading the session cookie?

const sessionStorage = createCookieSessionStorage({
  cookie: { name: 'mySession', secrets: ['s3cret'] }
});

const cookieHeader = 'mySession=eyJ1c2VySWQiOiIxMjM0NSJ9';
const session = await sessionStorage.getSession(cookieHeader);
const userId = session.get('userId');

medium

A. '12345'

B. undefined

C. null

D. Throws an error

Solution

1. Step 1: Decode the cookie value

   The cookie string 'mySession=eyJ1c2VySWQiOiIxMjM0NSJ9' is a base64-encoded JSON string representing {"userId":"12345"} but the session.get method expects keys set via session.set, not direct JSON parsing.

2. Step 2: Access session data with session.get('userId')

   Since the cookie is not properly signed/encrypted by Remix session storage, session.get('userId') returns undefined.

3. Final Answer:

   undefined -> Option B

4. Quick Check:

   session.get('userId') = undefined [OK]

Hint: Remember session.get(key) returns stored cookie value only if set via session.set [OK]

Common Mistakes:

• Assuming session.get returns undefined if cookie exists
• Confusing cookie string with session object
• Expecting an error from valid cookie data

4. Identify the error in this Remix cookie session code snippet:

const sessionStorage = createCookieSessionStorage({
  cookie: { name: 'session', secret: ['key1'] }
});

const session = await sessionStorage.getSession(request.headers.get('Cookie'));
session.set('token', 'abc123');
const cookieHeader = await sessionStorage.commitSession(session);
return new Response('OK', { headers: { 'Set-Cookie': cookieHeader } });

medium

A. session.set cannot be used to store values

B. Missing await before createCookieSessionStorage

C. The cookie option should use 'secrets' instead of 'secret'

D. Response headers should not include 'Set-Cookie'

Solution

1. Step 1: Check cookie options for session storage

   The correct option key is 'secrets' (plural), not 'secret'.

2. Step 2: Verify other code parts

   Await is not needed for createCookieSessionStorage, session.set is valid, and 'Set-Cookie' header is required to send cookie.

3. Final Answer:

   The cookie option should use 'secrets' instead of 'secret' -> Option C

4. Quick Check:

   Cookie option key = 'secrets' [OK]

Hint: Check cookie config keys carefully: 'secrets' not 'secret' [OK]

Common Mistakes:

• Using 'secret' instead of 'secrets' in cookie config
• Adding unnecessary await to createCookieSessionStorage
• Thinking session.set is invalid
• Removing 'Set-Cookie' header from response

5. You want to store a user's theme preference ('dark' or 'light') in a Remix cookie session and read it on page load. Which approach correctly sets and retrieves this value?

hard

A. Set the theme with session.set('theme', 'dark') before sending response; read with session.get('theme') after getting session from cookie

B. Store theme in localStorage and read it directly in the loader function

C. Use document.cookie to set theme and parse cookies manually in Remix loader

D. Save theme in a global variable and update it on each request

Solution

1. Step 1: Understand Remix cookie session usage

   Remix cookie sessions use session.set(key, value) to store data before sending response with Set-Cookie header.

2. Step 2: Retrieve stored data with session.get(key)

   On page load, get the session from cookie and read the theme with session.get('theme').

3. Final Answer:

   Set the theme with session.set('theme', 'dark') before sending response; read with session.get('theme') after getting session from cookie -> Option A

4. Quick Check:

   Use session.set and session.get for cookie session data [OK]

Hint: Use session.set before response and session.get after reading session [OK]

Common Mistakes:

• Using localStorage instead of cookie sessions in Remix loaders
• Manually parsing document.cookie instead of using session APIs
• Relying on global variables for per-user data