docs: clarify empty cookies when Cookie header is absent - #170
Open
Hashim1999164 wants to merge 1 commit into
Open
docs: clarify empty cookies when Cookie header is absent#170Hashim1999164 wants to merge 1 commit into
Hashim1999164 wants to merge 1 commit into
Conversation
Document that req.cookies and req.signedCookies are always empty
objects when no Cookie header is sent, so callers do not need to
guess between {}, false, or undefined.
Fixes expressjs#107
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Cookieheader is sent (or it is empty),req.cookiesandreq.signedCookiesare empty objects rather thanundefinedorfalse.Fixes #107
Test plan
index.jsthat both properties are set toObject.create(null)before the early return whenreq.headers.cookieis missing