- From: Daniel Stenberg <daniel@haxx.se>
- Date: Mon, 7 Mar 2016 13:09:20 +0100 (CET)
- To: Mike West <mkwst@google.com>
- cc: HTTP Working Group <ietf-http-wg@w3.org>, Samuel Huang <huangs@google.com>, Mark Nottingham <mnot@mnot.net>
On Mon, 7 Mar 2016, Daniel Stenberg wrote: > I was actually thinking of the case when 'Priority=High' or 'Priority=Low' > is used for an existing cookie, but I think I spoke up a little too early > about that since in the case of only one 'Priority' and no (other) cookie > name, it should indeed be distinguishable. (sorry for replying to myself) ...execept for older clients that don't know about these cookie priorities of course. For those, they will appear as duplicate cookie names in the headers and will most likely cause problems to legacy client-side implementations. libcurl will treat "Set-Cookie: Priority=Low; favcolor=blue" as a cookie named 'Priority' and discard the favcolor part. Reversing the string order will make it store 'favcolor' instead. Most surely other implementations will act differently. Thus, a server needs to know if the client supports Priority cookies before it can reliably send them. -- / daniel.haxx.se
Received on Monday, 7 March 2016 12:09:49 UTC