Google Chrome and Set-Cookie

Please tell me the correct format of the HTTP header Set-Cookie.
rfc2109 says:
 av-pairs = av-pair *(";" av-pair)
 av-pair = attr ["=" value] ; optional value
 attr = token
 value = word
 word = token | quoted-string
Send a GET request using Google Chrome at
Receive response with header:
Set-Cookie:SESSID="9l8MUBbPRhxaD2b9paYMGJ9t0Q9TLLYK"; Version="1"; Path="/"
Note the attribute Path="/". However, Chrome remembers the cookie with Path: /main
If the Path to send as a token and not a quoted-string, that is, Path=/, then everything works correctly.
Where are all the same the truth, and why does Google Chrome ignore the RFC?
October 3rd 19 at 04:10
1 answer
October 3rd 19 at 04:12
The new rfc6265 says nothing about quoted-string.
 path-av = "Path=" path-value
 path-value = <any char except ctls or ";">
And not even quotation marks:
If the attribute-value is empty or if the first character of the attribute-value is not %x2F ("/"):
Let cookie-path be the default-path.

Default path:
Output the characters of the uri-path from the first character up to, but not including, the right-most %x2F ("/").

So chrome all standard makes. - kaycee.Torphy commented on October 3rd 19 at 04:15

Find more questions by tags BrowsersC++Computer networksProgrammingRFC