- From: Kazuho Oku <kazuhooku@gmail.com>
- Date: Mon, 18 Jan 2016 23:46:34 +0900
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Stefan Eissing <stefan.eissing@greenbytes.de>, Martin Thomson <martin.thomson@gmail.com>, Ilya Grigorik <ilya@igvita.com>, Amos Jeffries <squid3@treenet.co.nz>, HTTP Working Group <ietf-http-wg@w3.org>
2016-01-18 19:32 GMT+09:00 Julian Reschke <julian.reschke@gmx.de>: > On 2016-01-18 11:19, Stefan Eissing wrote: >> >> +1 generic header parameter form. >> >> If I may make a proposal: >> >> Cache-Digest = "Cache-Digest" ":" #digest-value >> digest-value = "<" base64url encoded digest ">" *( ";" digest-param >> ) >> digest-param = ( ( "domain" "=" domain-value ) >> | ( "path" "=" path-value ) >> | ( "codec" "=" codec-value ) >> | ( "update" ( "=" update-param ) ) >> | ( digest-extension ) ) >> >> digest-extension = ( parmname [ "=" ( ptoken | quoted-string ) ] ) >> >> domain-value = >> authority # defined in RFC3986 >> | wildcard-identifier # defined in RFC 6125 6.4.3 >> >> path-value = path-absolute # defined in RFC3986 3.3 >> >> codec = ( "GCS-SHA256" | ( ptoken | quoted-string ) ) >> ... > > > I wouldn't use angle brackets here; let's leave them for use in places where > the value is a URI (Link header field and several WebDAV header fields). > > Just us token/quoted-sting here. > > Also, do not wire parameter names into the ABNF; this mixes syntax with > semantics. Thank you for the advice. Obviously I have used an old-fashioned RFC as a reference when writing the ABNF (that Stefan probably modified). I should have looked into a newer one, such as the Alt-Svc draft. > Best regards, Julian -- Kazuho Oku
Received on Monday, 18 January 2016 14:47:03 UTC