Hi, Only on the follow address to me:
On Tue, Jan 6, 2026 at 18:25 Lucas Pardue <[email protected]> wrote: > > > On Tue, Jan 6, 2026, at 15:39, Mallory Knodel via Datatracker wrote: > > * Not entirely clear from an implementation perspective what the > relationship > > would be between Accept-Encoding header field with identity, and the use of > Unencoded-digest. It's only briefly mentioned in describing the problem, > but > perhaps it would be conceptually useful for the reader to elaborate what > this > might look like in practice in Section 5. > > > So this one is a bit tricksy for a few reasons. > > Section 5 is titled "Messages containing both Unencoded-Digest and > Content-Encoding". If Accept-Encoding: identity were sent and respected, > there would be no Content-Encoding reaponse header (assuming the server > adheres to RFC 9110 [3].) > > There is some text in section 3 that touches on the matter [4] > > > The Unencoded-Digest HTTP field can be used in requests and responses > to communicate digests that are calculated using a hashing algorithm > applied to the entire selected representation data with no content codings > applied (Section 8.4.1 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__rfc-2Deditor.org_rfc_rfc9110-23section-2D8.4.1&d=DwMFAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=krANNudPSfUTEf2kXiduBUqRjXhDsKNCASr1kibHLfs&m=yLE8Q5d21pqtzP-lJt75NaxjX4ljliy4bzzmqQc8A3LoGThDcdo3rbpU6YkcVxyr&s=UjxWp4e3Kvx3oR2Io59Ds-p60IF9FqCOs2fSr6kTa50&e=> > of [HTTP > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_archive_id_draft-2Dietf-2Dhttpbis-2Dunencoded-2Ddigest-2D03.html-23HTTP&d=DwMFAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=krANNudPSfUTEf2kXiduBUqRjXhDsKNCASr1kibHLfs&m=yLE8Q5d21pqtzP-lJt75NaxjX4ljliy4bzzmqQc8A3LoGThDcdo3rbpU6YkcVxyr&s=-JsV74TBXejkNeCGz1DlZKQu8g9slnYyG9G4YC1jmFQ&e=> > ]). > > Apart from the content coding concerns, Unencoded-Digest behaves > similarly to Repr-Digest (Section 3 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__rfc-2Deditor.org_rfc_rfc9530-23section-2D3&d=DwMFAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=krANNudPSfUTEf2kXiduBUqRjXhDsKNCASr1kibHLfs&m=yLE8Q5d21pqtzP-lJt75NaxjX4ljliy4bzzmqQc8A3LoGThDcdo3rbpU6YkcVxyr&s=rFo1X_fbOR8FH_vuwe8TDVUHjvtvkDfer-O4Mm77NxY&e=> > of [DIGEST-FIELDS > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_archive_id_draft-2Dietf-2Dhttpbis-2Dunencoded-2Ddigest-2D03.html-23DIGEST-2DFIELDS&d=DwMFAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=krANNudPSfUTEf2kXiduBUqRjXhDsKNCASr1kibHLfs&m=yLE8Q5d21pqtzP-lJt75NaxjX4ljliy4bzzmqQc8A3LoGThDcdo3rbpU6YkcVxyr&s=484RkSdqGatmG_D63LGVKxmXzuehUfyaXs8ZTQEU25Y&e=>]). > In the absence of content codings, Unencoded-Digest is identical to > Repr-Digest. > > An earlier version of this draft [5] included an example that demonstrated > a response with both fields but the feedback was that it was a bit > contrived and unrealistic for a server to send three fields all with the > same value. > > The examples in section 6 take care to avoid that trap and contain > different values for each field to highlight the conceptual differences. > > I'm also a bit nervous about stepping onto a slippery slope of trying to > explain everythingb about HTTP semantics, especially if its "by example" > which can rarely be complete. > > Is there perhaps some succinct statement that could have aided you as a > reader ? I'd be happy to add some minor clarification or explocit assertion > somewhere. > Agreed that an example isn’t the way to go. The identity field for Accept-encoding is mentioned once. Maybe elaborating on the implications of that as it relates to the Unencoded-digest would be nice to have all in one place. I can’t finish that paragraph for you since I don’t know what you would say, but I found your explanation in this response off to a good start: “If Accept-Encoding: identity were sent and respected, there would be no Content-Encoding reaponse header (assuming the server adheres to RFC 9110 [3].)…” -Mallory > Cheers > Lucas > > > [1] https://github.com/httpwg/http-extensions/pull/3347 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_httpwg_http-2Dextensions_pull_3347&d=DwMFAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=krANNudPSfUTEf2kXiduBUqRjXhDsKNCASr1kibHLfs&m=yLE8Q5d21pqtzP-lJt75NaxjX4ljliy4bzzmqQc8A3LoGThDcdo3rbpU6YkcVxyr&s=B-JQCStrG43yWYP3HYm3ciJ1BVeov69N2ERWrvg9k5E&e=> > [2] https://httpwg.org/admin/editors/style-guide#reference-style > <https://urldefense.proofpoint.com/v2/url?u=https-3A__httpwg.org_admin_editors_style-2Dguide-23reference-2Dstyle&d=DwMFAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=krANNudPSfUTEf2kXiduBUqRjXhDsKNCASr1kibHLfs&m=yLE8Q5d21pqtzP-lJt75NaxjX4ljliy4bzzmqQc8A3LoGThDcdo3rbpU6YkcVxyr&s=3kPdG2G2BlVLpuQozck5RT8xRD7KaDVJlNih1onmZtw&e=> > [3] https://www.rfc-editor.org/rfc/rfc9110.html#section-8.4 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.rfc-2Deditor.org_rfc_rfc9110.html-23section-2D8.4&d=DwMFAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=krANNudPSfUTEf2kXiduBUqRjXhDsKNCASr1kibHLfs&m=yLE8Q5d21pqtzP-lJt75NaxjX4ljliy4bzzmqQc8A3LoGThDcdo3rbpU6YkcVxyr&s=qWPN_yGLhgW5AyUBfaLOiCMh83Y-j49l2ObVmAQwEco&e=> > [4] > https://www.ietf.org/archive/id/draft-ietf-httpbis-unencoded-digest-03.html#section-3-2 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_archive_id_draft-2Dietf-2Dhttpbis-2Dunencoded-2Ddigest-2D03.html-23section-2D3-2D2&d=DwMFAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=krANNudPSfUTEf2kXiduBUqRjXhDsKNCASr1kibHLfs&m=yLE8Q5d21pqtzP-lJt75NaxjX4ljliy4bzzmqQc8A3LoGThDcdo3rbpU6YkcVxyr&s=y37xzE9g4YDAoQMEnaIvRjLP5NUTabZGb0eZj7l8FWA&e=> > [5] > https://www.ietf.org/archive/id/draft-pardue-http-identity-digest-01.html > <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_archive_id_draft-2Dpardue-2Dhttp-2Didentity-2Ddigest-2D01.html&d=DwMFAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=krANNudPSfUTEf2kXiduBUqRjXhDsKNCASr1kibHLfs&m=yLE8Q5d21pqtzP-lJt75NaxjX4ljliy4bzzmqQc8A3LoGThDcdo3rbpU6YkcVxyr&s=MQzSxCNfFJROfvQR_Yv9lUU6SOsDQrsfIm0wOdOcc58&e=> >
_______________________________________________ Gen-art mailing list -- [email protected] To unsubscribe send an email to [email protected]
