[feature] Implement request.getCookie(name)

[uasan]

Hey. You have implemented the request.getQuery(name) method with optional argument.

Often need a method request.getCookie(name). The best i could come up with in JS:

import { parse } from 'querystring';

parse(request.getHeader('cookie'), '; ')

But, parsing cookies in JS is not productive. It will be great if the method getCookie(name) appears in request object and is as efficient as getQuery(name). Thanks.

[hst-m]

this is what I use:

const getCookie=(req,name)=>(req.cookies??=req.getHeader('cookie')).match(getCookie[name]??=new RegExp(`(^|;)\\s*${name}\\s*=\\s*([^;]+)`))?.[2]

// example
getCookie(req,'cookieName')

I tested this vs querystring.parse method, I show 370 nanoseconds for my getCookie and 1700 nanosec for querystring.parse, req.getHeader('cookie') takes up 210 ns of each

[uasan]

querystring.parse - this method parses all cookies from the header line and decodeURIComponent() their values, I think this is the time difference

[ghost]

This could make sense if getCookie is often used. It looks to be similar to getQuery - but there is no docs saying it should be URI decoded (some say it should be base64).

[uasan]

no docs saying it should be URI decoded (some say it should be base64).

Yes, this is not part of the specification, this is the actual (historically) implementation for encoding special characters, but for many business logic, normal raw implementation - without decoding