From 6d38a0e64c834f5cbf945acb4f1982471da61661 Mon Sep 17 00:00:00 2001 From: Lucas Pardue Date: Tue, 3 Feb 2026 11:04:35 +0000 Subject: [PATCH] Address genart review feedback --- draft-ietf-httpbis-unencoded-digest.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/draft-ietf-httpbis-unencoded-digest.md b/draft-ietf-httpbis-unencoded-digest.md index ca80816fa..28e489da1 100644 --- a/draft-ietf-httpbis-unencoded-digest.md +++ b/draft-ietf-httpbis-unencoded-digest.md @@ -135,8 +135,12 @@ entire selected representation data with no content codings applied ({{Section 8.4.1 of HTTP}}). Apart from the content coding concerns, `Unencoded-Digest` behaves similarly -to `Repr-Digest` ({{Section 3 of DIGEST-FIELDS}}). In the absence of content -codings, `Unencoded-Digest` is identical to `Repr-Digest`. +to `Repr-Digest` ({{Section 3 of DIGEST-FIELDS}}). + +`Unencoded-Digest` can be sent in messages with and without content codings. +When there is no content coding, `Unencoded-Digest` acts identically to +`Repr-Digest`; for the same hashing algorithm the computed value would be the +same. `Unencoded-Digest` is a `Dictionary` (see {{Section 3.2 of STRUCTURED-FIELDS}}) where each: @@ -290,7 +294,7 @@ ca cc 4b e7 02 00 7e af 07 44 ~~~ {: title="GET response with GZIP content coding"} -The second example demonstrates a range request with content negotiation. +The second example demonstrates a range request that uses content negotiation. ~~~ http-message GET /boringstring HTTP/1.1