Cookie session storage in Remix

Introduction

Cookie session storage helps keep user data safe between pages using small files stored in the browser. It lets your app remember who the user is without asking again.

Remembering if a user is logged in while they browse your site.

Saving user preferences like theme or language during a visit.

Keeping track of items in a shopping cart before checkout.

Storing temporary data that should disappear after the browser closes.

Syntax

Remix

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

const sessionStorage = createCookieSessionStorage({
  cookie: {
    name: 'session',
    secrets: ['your-secret-key'],
    sameSite: 'lax',
    path: '/',
    httpOnly: true,
    secure: process.env.NODE_ENV === 'production',
  },
});

The secrets array is used to sign cookies for security.

Set secure to true only in production to use HTTPS.

Examples

This example shows how to create a session, store a user ID, and send the cookie back to the browser.

Remix

const session = await sessionStorage.getSession(request.headers.get('Cookie'));
session.set('userId', '12345');
const cookieHeader = await sessionStorage.commitSession(session);

return new Response('Logged in', {
  headers: { 'Set-Cookie': cookieHeader },
});

This example reads the user ID from the session cookie and responds accordingly.

Remix

const session = await sessionStorage.getSession(request.headers.get('Cookie'));
const userId = session.get('userId');

if (!userId) {
  return new Response('Not logged in', { status: 401 });
}

return new Response(`Welcome user ${userId}`);

Sample Program

This Remix loader function counts how many times a user visits the page by storing a number in a cookie session. Each time the page loads, it reads the count, adds one, and saves it back.

Remix

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

const sessionStorage = createCookieSessionStorage({
  cookie: {
    name: 'session',
    secrets: ['my-secret-key'],
    sameSite: 'lax',
    path: '/',
    httpOnly: true,
    secure: false,
  },
});

export async function loader({ request }) {
  const session = await sessionStorage.getSession(request.headers.get('Cookie'));
  const visits = session.get('visits') ?? 0;
  session.set('visits', visits + 1);
  const cookieHeader = await sessionStorage.commitSession(session);

  return new Response(`You have visited this page ${visits + 1} times.`, {
    headers: { 'Set-Cookie': cookieHeader },
  });
}

Important Notes

Always keep your secret keys safe and never share them publicly.

Use httpOnly to prevent JavaScript from accessing cookies, improving security.

Remember to set secure to true when deploying to production with HTTPS.

Summary

Cookie session storage keeps user data between page visits using browser cookies.

It helps remember users and their preferences safely.

Remix provides easy tools to create, read, and update cookie sessions.

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