Important: This documentation covers Yarn 1 (Classic).
For Yarn 2+ docs and migration guide, see yarnpkg.com.

Package detail

cookie-parser

expressjs17.3mMIT1.4.7TypeScript support: definitely-typed

Parse HTTP request cookies

cookie, middleware

readme

cookie-parser

NPM Version NPM Downloads Build Status Test Coverage

Parse Cookie header and populate req.cookies with an object keyed by the cookie names. Optionally you may enable signed cookie support by passing a secret string, which assigns req.secret so it may be used by other middleware.

Installation

$ npm install cookie-parser

API

var cookieParser = require('cookie-parser')

cookieParser(secret, options)

Create a new cookie parser middleware function using the given secret and options.

  • secret a string or array used for signing cookies. This is optional and if not specified, will not parse signed cookies. If a string is provided, this is used as the secret. If an array is provided, an attempt will be made to unsign the cookie with each secret in order.
  • options an object that is passed to cookie.parse as the second option. See cookie for more information.
    • decode a function to decode the value of the cookie

The middleware will parse the Cookie header on the request and expose the cookie data as the property req.cookies and, if a secret was provided, as the property req.signedCookies. These properties are name value pairs of the cookie name to cookie value.

When secret is provided, this module will unsign and validate any signed cookie values and move those name value pairs from req.cookies into req.signedCookies. A signed cookie is a cookie that has a value prefixed with s:. Signed cookies that fail signature validation will have the value false instead of the tampered value.

In addition, this module supports special "JSON cookies". These are cookie where the value is prefixed with j:. When these values are encountered, the value will be exposed as the result of JSON.parse. If parsing fails, the original value will remain.

cookieParser.JSONCookie(str)

Parse a cookie value as a JSON cookie. This will return the parsed JSON value if it was a JSON cookie, otherwise, it will return the passed value.

cookieParser.JSONCookies(cookies)

Given an object, this will iterate over the keys and call JSONCookie on each value, replacing the original value with the parsed value. This returns the same object that was passed in.

cookieParser.signedCookie(str, secret)

Parse a cookie value as a signed cookie. This will return the parsed unsigned value if it was a signed cookie and the signature was valid. If the value was not signed, the original value is returned. If the value was signed but the signature could not be validated, false is returned.

The secret argument can be an array or string. If a string is provided, this is used as the secret. If an array is provided, an attempt will be made to unsign the cookie with each secret in order.

cookieParser.signedCookies(cookies, secret)

Given an object, this will iterate over the keys and check if any value is a signed cookie. If it is a signed cookie and the signature is valid, the key will be deleted from the object and added to the new object that is returned.

The secret argument can be an array or string. If a string is provided, this is used as the secret. If an array is provided, an attempt will be made to unsign the cookie with each secret in order.

Example

var express = require('express')
var cookieParser = require('cookie-parser')

var app = express()
app.use(cookieParser())

app.get('/', function (req, res) {
  // Cookies that have not been signed
  console.log('Cookies: ', req.cookies)

  // Cookies that have been signed
  console.log('Signed Cookies: ', req.signedCookies)
})

app.listen(8080)

// curl command that sends an HTTP request with two cookies
// curl http://127.0.0.1:8080 --cookie "Cho=Kim;Greet=Hello"

License

MIT

changelog

1.4.7 / 2024-10-08

  • deps: cookie@0.7.2
    • Fix object assignment of hasOwnProperty
  • deps: cookie@0.7.1
    • Allow leading dot for domain
      • Although not permitted in the spec, some users expect this to work and user agents ignore the leading dot according to spec
    • Add fast path for serialize without options, use obj.hasOwnProperty when parsing
  • deps: cookie@0.7.0
    • perf: parse cookies ~10% faster
    • fix: narrow the validation of cookies to match RFC6265
    • fix: add main to package.json for rspack
  • deps: cookie@0.6.0
    • Add partitioned option
  • deps: cookie@0.5.0
    • Add priority option
    • Fix expires option to reject invalid dates
    • pref: improve default decode speed
    • pref: remove slow string split in parse
  • deps: cookie@0.4.2
    • pref: read value only when assigning in parse
    • pref: remove unnecessary regexp in parse

1.4.6 / 2021-11-16

1.4.5 / 2020-03-14

1.4.4 / 2019-02-12

  • perf: normalize secret argument only once

1.4.3 / 2016-05-26

1.4.2 / 2016-05-20

  • deps: cookie@0.2.4
    • perf: enable strict mode
    • perf: use for loop in parse
    • perf: use string concatenation for serialization

1.4.1 / 2016-01-11

1.4.0 / 2015-09-18

  • Accept array of secrets in addition to a single secret
  • Fix JSONCookie to return undefined for non-string arguments
  • Fix signedCookie to return undefined for non-string arguments
  • deps: cookie@0.2.2

1.3.5 / 2015-05-19

1.3.4 / 2015-02-15

1.3.3 / 2014-09-05

1.3.2 / 2014-06-26

1.3.1 / 2014-06-17

  • actually export signedCookie

1.3.0 / 2014-06-17

  • add signedCookie export for single cookie unsigning

1.2.0 / 2014-06-17

  • export parsing functions
  • req.cookies and req.signedCookies are now plain objects
  • slightly faster parsing of many cookies

1.1.0 / 2014-05-12

  • Support for NodeJS version 0.8
  • deps: cookie@0.1.2
    • Fix for maxAge == 0
    • made compat with expires field
    • tweak maxAge NaN error message

1.0.1 / 2014-02-20

  • add missing dependencies

1.0.0 / 2014-02-15

  • Genesis from connect