HttpOnly Cookies

In this lesson you will learn httponly cookies in authentication, why it matters within cookies, and how to use it correctly with clear, copy-ready examples.

HttpOnly Cookies Overview

HttpOnly Cookies lets you structure authentication work so it stays readable, testable, and easy to scale. Instead of ad-hoc code, you follow a clear pattern that other developers can recognise immediately.

The key is to keep httponly cookies focused and predictable. Start from the minimal example here, then layer in only the complexity your feature actually needs.

import session from 'express-session';

app.use(session({
  secret: process.env.SESSION_SECRET,
  resave: false,
  saveUninitialized: false,
  cookie: { httpOnly: true, secure: true, sameSite: 'lax', maxAge: 3600000 },
}));

app.post('/login', (req, res) => {
  req.session.userId = user.id;
  res.json({ ok: true });
});

Session auth stores a server-side session and sends the user a secure, httpOnly cookie.

HttpOnly Cookies Example

// verify the caller on every protected request
function authenticate(req, res, next) {
  const token = req.headers.authorization?.replace('Bearer ', '');
  req.user = verifyToken(token); // throws if invalid
  next();
}

Start from a minimal HttpOnly Cookies example and grow it only as needed.
Keep configuration explicit so HttpOnly Cookies behaves the same in every environment.
Name things clearly so teammates understand your HttpOnly Cookies at a glance.
Add tests around HttpOnly Cookies early to lock in expected behaviour.

Authentication Cheatsheet

Quick authentication reference related to httponly cookies.

Concept	Example	Purpose
Hash password	`bcrypt.hash(pw, 12)`	Store credentials safely
Issue JWT	`jwt.sign(claims, secret)`	Stateless access token
Verify JWT	`jwt.verify(token, secret)`	Trust the caller
Session	`req.session.userId = id`	Server-side login state
Cookie	`httpOnly, secure, sameSite`	Protect the session token
Authorize	`requireRole('admin')`	Control what users can do
MFA	`authenticator.verify(...)`	Add a second factor

How HttpOnly Cookies Works

HttpOnly Cookies is part of proving who a user is and what they are allowed to do. Authentication verifies identity, while authorization decides access — and httponly cookies plays a specific role in that flow.

Session auth stores a server-side session and sends the user a secure, httpOnly cookie.

Never store or log plain-text passwords or secrets.
Prefer short-lived tokens with refresh over long-lived ones.
Always send credentials over HTTPS.
Fail closed: deny access when anything is uncertain.

Security Guidance for HttpOnly Cookies

Security is the whole point of httponly cookies. Small mistakes — weak hashing, tokens in localStorage, missing rate limits — are exactly what attackers look for, so follow proven defaults.

Risk	Mitigation
Credential theft	Strong hashing, MFA, HTTPS only
Token leakage	httpOnly cookies, short TTLs
Brute force	Rate limiting and lockouts
Privilege abuse	Least-privilege authorization checks

Common Mistakes

Copying httponly cookies snippets without understanding what each line does.
Skipping error handling and edge cases when wiring up httponly cookies.
Leaving httponly cookies untested, so regressions slip into production.
Over-engineering httponly cookies before you actually need the extra flexibility.

Key Takeaways

HttpOnly Cookies is a core part of working effectively with authentication.
Start small and keep httponly cookies focused on a single responsibility.
Apply consistent patterns so httponly cookies scales across your project.
Test and document httponly cookies to keep it maintainable over time.

Pro Tip

When you get stuck on httponly cookies, reduce it to the smallest reproducible example first — most authentication issues become obvious once the noise is gone.