Skip to content

Commit a56bf85

Browse files
authored
[RFC6265bis] Accept max-age=0
As noted in #3375, the server-side requirements for `set-cookie` headers define a grammar that explicitly excludes "0" as a valid value for the `max-age` attribute. This doesn't match either current client behavior, or widespread developer practice for cookie removal (see [1]). [1]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Cookies
1 parent e0dca34 commit a56bf85

1 file changed

Lines changed: 1 addition & 3 deletions

File tree

draft-ietf-httpbis-rfc6265bis.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -620,9 +620,7 @@ cookie-av = expires-av / max-age-av / domain-av /
620620
expires-av = "Expires" BWS "=" BWS sane-cookie-date
621621
sane-cookie-date =
622622
<IMF-fixdate, defined in [HTTP], Section 5.6.7>
623-
max-age-av = "Max-Age" BWS "=" BWS non-zero-digit *DIGIT
624-
non-zero-digit = %x31-39
625-
; digits 1 through 9
623+
max-age-av = "Max-Age" BWS "=" BWS 1*DIGIT
626624
domain-av = "Domain" BWS "=" BWS domain-value
627625
domain-value = <subdomain>
628626
; see details below

0 commit comments

Comments
 (0)