- From: Roberto Polli <robipolli@gmail.com>
- Date: Tue, 30 Jun 2020 18:03:25 +0200
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
Hi Julian,
thanks for this feedback!
I am reading RFC 6920 but I don't find many details on representation
metadata and partial representation
(only `ct` - content-type is defined).
It would be interesting to understand how to tie "ni:///$HASH" with
the other digest-algorithms in a way that it is respectful of RFC3230,
eg. see https://github.com/httpwg/http-extensions/pull/1213
When I finish reading rfc 6920 I'll provide more feedback.
Thanks again,
R.
Il giorno mar 30 giu 2020 alle ore 11:26 Julian Reschke
<julian.reschke@gmx.de> ha scritto:
> I just noticed that RFC 4918 (WebDAV) and RFC 6920 (Naming Things with
> Hashes) give us the machinery to make request conditional on hashes.
>
> Example (based on
> <https://greenbytes.de/tech/webdav/draft-ietf-httpbis-digest-headers-02.html#server-returns-full-representation-data>)
>
> PUT /x HTTP/1.1
> Host: foo
> If: <ni:///sha-256;X48E9qOokqqrvdts8nOJRJN3OWDUoyWxBf7kbu9DBPE=>
> Content-Type: application/json
>
> {"hello": "world2"}
>
> All that would be needed is s statement that servers that support both
> the Digest field and the If header field SHOULD consider the ni: URIs
> built from the hashes as "state tokens" as defined in RFC 4918, Section 3.
>
> Best regards, Julian
>
Received on Tuesday, 30 June 2020 16:04:21 UTC