【发布时间】:2013-04-24 17:20:59
【问题描述】:
通常,浏览器将 cookie 分组到单个 Cookie 标头中,例如:
Cookie: a=1; b=2
标准是否允许将这些作为单独的标头发送,例如:
Cookie: a=1
Cookie: b=2
或者他们总是必须在同一行?
【问题讨论】:
通常,浏览器将 cookie 分组到单个 Cookie 标头中,例如:
Cookie: a=1; b=2
标准是否允许将这些作为单独的标头发送,例如:
Cookie: a=1
Cookie: b=2
或者他们总是必须在同一行?
【问题讨论】:
在查找有关该主题的详细信息时偶然访问了此页面。来自HTTP State Management Mechanism、RFC 6265 的引用应该会让事情更清楚:
5.4。 Cookie 标头
当用户代理生成一个 HTTP 请求时,用户代理必须 不要附加多个 Cookie 标头字段。
貌似使用多个Cookie headers是,其实是禁止的!
【讨论】:
Set-Cookie 标头进行响应:tools.ietf.org/html/rfc6265#page-7
Set-Cookie:a=b;c=d; 比Set-Cookie:a=b; Set-Cookie:c=d; 更正确。规范说服务器不应该将多个 Set-Cookie 标头字段折叠到一个 field 中,但它可以将多个 Set-Cookie 标头字段添加到一个 response 中。这在现实世界中意味着,当代理服务器传递响应时,如果该代理设置了 cookie,它应该使用单独的 Set-Cookie 标头。
它现在在 HTTP/2 (RFC 7540) 中被允许,它指定:
8.1.2.5. Compressing the Cookie Header Field
The Cookie header field [COOKIE] uses a semi-colon (";") to delimit
cookie-pairs (or "crumbs"). This header field doesn't follow the
list construction rules in HTTP (see [RFC7230], Section 3.2.2), which
prevents cookie-pairs from being separated into different name-value
pairs. This can significantly reduce compression efficiency as
individual cookie-pairs are updated.
To allow for better compression efficiency, the Cookie header field
MAY be split into separate header fields, each with one or more
cookie-pairs. If there are multiple Cookie header fields after
decompression, these MUST be concatenated into a single octet string
using the two-octet delimiter of 0x3B, 0x20 (the ASCII string "; ")
before being passed into a non-HTTP/2 context, such as an HTTP/1.1
connection, or a generic HTTP server application.
Therefore, the following two lists of Cookie header fields are
semantically equivalent.
cookie: a=b; c=d; e=f
cookie: a=b
cookie: c=d
cookie: e=f
【讨论】: