W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2017

Re: making up new header field syntax...

From: Julian Reschke <julian.reschke@gmx.de>
Date: Sun, 25 Jun 2017 13:57:43 +0200
To: HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <32e0bb44-54c2-d6a7-c14a-452738246e4d@gmx.de>
On 2017-06-25 13:52, Julian Reschke wrote:
> Here's a recent example I found (when looking for uses of JFV):
> 
> <https://w3c.github.io/webappsec-clear-site-data/#header>:
> 
>> The Clear-Site-Data HTTP response header field sends a signal to the 
>> user agent that it ought to remove all data of a certain set of types. 
>> The header is represented by the following ABNF [RFC5234]:
>>
>> Clear-Site-Data = 1#( DQUOTE ( data-type | extension-type ) DQUOTE )
>> data-type = "cache" | "cookies" | "storage" | "executionContexts"
>> extension-type = 1*( ALPHA | "-")
>> ; #rule is defined in Section 7 of RFC 7230.
>> ; DQUOTE and ALPHA are defined in Appendix B.1 of RFC 5234.
> 
> Issues:
> 
> a) the list rule is defined in RFC 7230, not RFC 5234
> 
> b) the syntax doesn't allow whitespace, but the examples use it
> 
> c) things look like quoted-strings, but aren't quoted-strings
> 
> d) tokens not allowed
> 
> Best regards, Julian

e) ABNF invalid ("|" instead of "/" - 
<https://www.youtube.com/watch?v=LbK-g8tKnoc>)

Best regards, Julian
Received on Sunday, 25 June 2017 11:58:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:15:03 UTC