- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Sun, 9 Aug 2015 21:34:56 +0200
- To: Mike West <mkwst@google.com>
- Cc: "public-webappsec@w3.org" <public-webappsec@w3.org>
On 2015-08-09 09:31, Mike West wrote: > Hey Julian! Thanks for the feedback! > > On Wed, Aug 5, 2015 at 9:15 PM, Julian Reschke <julian.reschke@gmx.de > <mailto:julian.reschke@gmx.de>> wrote: > > Hi there, > > on <http://www.w3.org/TR/2015/WD-clear-site-data-20150804/#header>...: > > I'm concerned that this is yet another complex header field syntax > that requires a custom parser to handle properly. Please consider > reusing the syntax of something that already exists, such as "Prefer" > > > I'm trying to parse the `Prefer` ABNF (defined in > http://tools.ietf.org/html/rfc7240#section-2). It says that `token` and > `word` are defined within Sections 3.2.1 and 3.2.4 of [RFC7230], but > they don't appear to actually be defined there. Can you point me to the > correct reference (I assume `token` is from > http://tools.ietf.org/html/rfc7230#section-3.2.6, but I can't find `word`)? > > or to adopt JSON (see > <http://greenbytes.de/tech/webdav/draft-reschke-http-jfv-latest.html>). > > > Hrm. The response to this seemed mixed at the workshop (though I came > into the presentation late). How much support is there in general? Would None yet. > this be the only JSON header? I'd prefer not to break new ground in > header syntax... :) It is "new ground" everytime you use a syntax that doesn't already have a parser :-) > ... Best regards, Julian
Received on Sunday, 9 August 2015 19:35:26 UTC