You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This patch incorporates two ABNF changes:
1. Closes#1074 by
adjusting the `cookie-pair` grammar to include optional spaces.
We test this behavior in a few distinct WPTs, including
chromium0014, name0018, value0006.
2. Closes#1119
by removing OWS from the spec, as user agents generally follow
the "SHOULD" in the current text to limit themselves to a single
SP rather than serializing with OWS. It's reasonable to lock that
in, and it also happens to match all the `Cookie:` header tests
we have.
Thanks to both @reschke and @bakulf for paying attention to this.
This patch incorporates two ABNF changes:
1. Closes#1074 by
adjusting the `cookie-pair` grammar to include optional spaces.
We test this behavior in a few distinct WPTs, including
chromium0014, name0018, value0006.
2. Closes#1119
by removing OWS from the spec, as user agents generally follow
the "SHOULD" in the current text to limit themselves to a single
SP rather than serializing with OWS. It's reasonable to lock that
in, and it also happens to match all the `Cookie:` header tests
we have.
Thanks to both @reschke and @bakulf for paying attention to this.
Similar to #1073, by spec, cookie name and value should not contain spaces, but modern browsers do allow spaces. We even have WPTs.
A similar issue is the trimming of cookie-name and cookie-value. By spec: "SetCookie: foo = bar" is invalid.
What I suggest is to write the BFN in this way (untested, unverified):
The text was updated successfully, but these errors were encountered: