- From: Mike Taylor <miketaylr@google.com>
- Date: Mon, 24 Feb 2025 09:23:18 -0500
- To: Daniel Stenberg <daniel@haxx.se>
- Cc: Anne van Kesteren <annevk@annevk.nl>, Yoav Weiss <yoav.weiss@shopify.com>, HTTP Working Group <ietf-http-wg@w3.org>, Patrick Meenan <patmeenan@gmail.com>, Steven Bingler <bingler@google.com>, רועי ברקאי <roybarkayyosef@gmail.com>, Watson Ladd <watsonbladd@gmail.com>, Yoav Weiss <yoav@yoav.ws>, Rory Hewitt <rory.hewitt@gmail.com>, Colin Bendell <colin.bendell@shopify.com>, Joakim Erdfelt <joakim@webtide.com>
On 2/24/25 6:18 AM, Daniel Stenberg wrote: > On Mon, 24 Feb 2025, Joakim Erdfelt wrote: > >> RFC6265 states a `cookie-name` is a `token` as defined by RFC2616 >> https://www.rfc-editor.org/rfc/rfc6265#section-4.1.1 > > ... and once again the cookie spec turns out to be hard to read... How should the editors interpret this feedback to be actionable?
Received on Monday, 24 February 2025 14:23:24 UTC