Skip to content

Address genart review feedback #3387

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
LPardue wants to merge 1 commit into
base: main
Choose a base branch
from
+7 −3
Open

Address genart review feedback #3387

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions draft-ietf-httpbis-unencoded-digest.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down Expand Up @@ -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
Expand Down