Menu
Semicolon ;, the Cookie: string or some other string?
673
Each cookie is separated by a comma , and each cookie attributes are separated by semicolons ; . The two values required are the first name=value pair which are always string values.
The Cookie HTTP request header contains stored HTTP cookies associated with the server (i.e. previously sent by the server with the Set-Cookie header or set in JavaScript using Document. cookie ). The Cookie header is optional and may be omitted if, for example, the browser's privacy settings block cookies.
The Set-Cookie HTTP response header is used to send a cookie from the server to the user agent, so that the user agent can send it back to the server later.
The cookie file is stored in the user's browser application data folder. Later, the browser automatically sends this cookie as part of the request.
The Cookie: header has the following syntax:
Cookie: <Name> = <Value> { ; <Name> = <Value> }
Hence individual cookies are separated with the semicolon and a space.
On the other hand, when setting a cookie in the response, there one cookie per the Set-Cookie: header:
Set-Cookie: <Name> = <Value> [ ; expires = <Date>] [ ; path = <Path> ] [ ; domain = <Domain> ] // etc…
To set multiple cookies the Set-Cookie header is repeated in an HTTP response.
Notes:
Cookie2 and Set-Cookie2 which were abandoned.Set-Cookie (or Set-Cookie2) headers into one. However, this folding is not recommended by the latest RFC 6265 spec.
153
The answer is a comma , sign.
In section 4.2.2 of RFC 2109 there's this specification of Set-Cookie header
set-cookie = "Set-Cookie:" cookies
cookies = 1#cookie
with the following statement Informally, the Set-Cookie response header comprises the token Set-Cookie:, followed by a comma separated list of one or more cookies. (Formally meaning of # in the above notation is defined in RFC 733 in section A. NOTATIONAL CONVENTIONS, point 5
A construct "#" is defined, similar to "*", as follows:
<l>#<m>elementindicating at least
<l>and at most<m>elements, each separated by one or more commas (",").
Yes, RFC 2109 was obsoleted by RFC 2965, which in turn was obsoleted by RFC 6265.
No, it doesn't change anything in this context as
Set-Cookie folding
22
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
