> On 13 Jan 2016, at 09:40, Stefan Eissing <stefan.eissing@greenbytes.de> wrote: > > ... > Cache-Digest: <base64url encoded, golombset compressed digests> > Connection: Cache-Digest > ... > > The question is what a H2 origin server does with such a header, > should it appear. Ignore, discard? According to RFC 7540 a H2 origin server would have to reject that stream with RST_STREAM(PROTOCOL_ERROR): see Section 8.1.2.2 for the normative MUST NOT. For that reason, I think this is a reasonable extension but *only* if the header is defined as connection-specific. Assuming that Kazuho’s objections relating to XMLHttpRequest and FetchAPI are resolved, this approach seems reasonable. One approach to resolving those problems would be to add a requirement that H2 endpoints treat a stream with the Cache-Digest header in it as a stream error with some useful error flag. That requirement, well policed by origin servers, would probably resolve the issue neatly. Cory
Received on Thursday, 14 January 2016 11:13:25 UTC