From be042ee5ef4e4c724f0f5c2cc4ffb4ca241ec27d Mon Sep 17 00:00:00 2001 From: ID Bot Date: Thu, 27 Jun 2024 15:55:13 +0000 Subject: [PATCH] Script updating gh-pages from 4b65e13. [ci skip] --- draft-kleidl-digest-fields-problem-types.html | 57 ++++++++++++++++++- draft-kleidl-digest-fields-problem-types.txt | 53 ++++++++++++++++- 2 files changed, 107 insertions(+), 3 deletions(-) diff --git a/draft-kleidl-digest-fields-problem-types.html b/draft-kleidl-digest-fields-problem-types.html index 603c969..4a7ca1f 100644 --- a/draft-kleidl-digest-fields-problem-types.html +++ b/draft-kleidl-digest-fields-problem-types.html @@ -1134,6 +1134,9 @@

{ "type": "https://iana.org/assignments/http-problem-types#unsupported-hashing-algorithm", - "title": "upload is already completed", + "title": "hashing algorithm is not supported", "unsupported-algorithm": "foo", "supported-algorithms": ["sha-256", "sha-512"] } +

If the sender receives this problem type, it SHOULD retry the request while picking another hashing algorithm. If the response includes an array of supported algorithms, it SHOULD choose one of them.

+ + +
+
+

+3.2. Invalid Digest Value +

+

This section defines the https://iana.org/assignments/http-problem-types#invalid-digest-value problem type [PROBLEM]. A resource MAY use this problem type in a response to a request, whose integrity fields include a digest value, that cannot be generated by the corresponding hashing algorithm. For example, if the digest value of the sha-512 hashing algorithm is not 64 bytes long, it cannot be a valid digest value and the resource can skip computing the digest value.

+

The resource SHOULD a human-readable description why the value is considered invalid in the title member.

+

The following example shows a response for a request with an invalid digest value.

+
+
+HTTP/1.1 400 Bad Request
+Content-Type: application/problem+json
+
+{
+  "type": "https://iana.org/assignments/http-problem-types#invalid-digest-value",
+  "title": "digest value for sha-512 is not 64 bytes long"
+}
+
+
+

If the sender receives this problem type, it SHOULD NOT retry the request without modification. Such an error is likely rooted in a fault in the sender's computation or encoding of the digest value.

@@ -1259,6 +1285,29 @@

+

IANA is asked to register the following entry in the "HTTP Problem Types" registry:

+
+
Type URI:
+
+

https://iana.org/assignments/http-problem-types#invalid-digest-value

+
+
+
Title:
+
+

Invalid Digest Value

+
+
+
Recommended HTTP status code:
+
+

400

+
+
+
Reference:
+
+

This document

+
+
+
@@ -1284,9 +1333,13 @@

Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/rfc/rfc8174>.
[RFC9530]
-
+
Polli, R. and L. Pardue, "Digest Fields", RFC 9530, DOI 10.17487/RFC9530, , <https://www.rfc-editor.org/rfc/rfc9530>.
+
[STRUCTURED-FIELDS]
+
+Nottingham, M. and P. Kamp, "Structured Field Values for HTTP", RFC 8941, DOI 10.17487/RFC8941, , <https://www.rfc-editor.org/rfc/rfc8941>.
+

diff --git a/draft-kleidl-digest-fields-problem-types.txt b/draft-kleidl-digest-fields-problem-types.txt index c10f809..19f7209 100644 --- a/draft-kleidl-digest-fields-problem-types.txt +++ b/draft-kleidl-digest-fields-problem-types.txt @@ -65,6 +65,7 @@ Table of Contents 2. Conventions and Definitions 3. Problem Types 3.1. Unsupported Hashing Algorithm + 3.2. Invalid Digest Value 4. Security Considerations 5. IANA Considerations 6. Normative References @@ -156,11 +157,44 @@ Table of Contents { "type": "https://iana.org/assignments/http-problem-types#unsupported-hashing-algorithm", - "title": "upload is already completed", + "title": "hashing algorithm is not supported", "unsupported-algorithm": "foo", "supported-algorithms": ["sha-256", "sha-512"] } + If the sender receives this problem type, it SHOULD retry the request + while picking another hashing algorithm. If the response includes an + array of supported algorithms, it SHOULD choose one of them. + +3.2. Invalid Digest Value + + This section defines the https://iana.org/assignments/http-problem- + types#invalid-digest-value problem type [PROBLEM]. A resource MAY + use this problem type in a response to a request, whose integrity + fields include a digest value, that cannot be generated by the + corresponding hashing algorithm. For example, if the digest value of + the sha-512 hashing algorithm is not 64 bytes long, it cannot be a + valid digest value and the resource can skip computing the digest + value. + + The resource SHOULD a human-readable description why the value is + considered invalid in the title member. + + The following example shows a response for a request with an invalid + digest value. + + HTTP/1.1 400 Bad Request + Content-Type: application/problem+json + + { + "type": "https://iana.org/assignments/http-problem-types#invalid-digest-value", + "title": "digest value for sha-512 is not 64 bytes long" + } + + If the sender receives this problem type, it SHOULD NOT retry the + request without modification. Such an error is likely rooted in a + fault in the sender's computation or encoding of the digest value. + 4. Security Considerations Although an error appeared while handling the digest fields, the @@ -184,6 +218,18 @@ Table of Contents Reference: This document + IANA is asked to register the following entry in the "HTTP Problem + Types" registry: + + Type URI: https://iana.org/assignments/http-problem-types#invalid- + digest-value + + Title: Invalid Digest Value + + Recommended HTTP status code: 400 + + Reference: This document + 6. Normative References [DIGEST] Polli, R. and L. Pardue, "Digest Fields", RFC 9530, @@ -207,6 +253,11 @@ Table of Contents DOI 10.17487/RFC9530, February 2024, . + [STRUCTURED-FIELDS] + Nottingham, M. and P. Kamp, "Structured Field Values for + HTTP", RFC 8941, DOI 10.17487/RFC8941, February 2021, + . + Acknowledgments TODO acknowledge.