tus / draft-digest-fields-problem-types

An Internet Draft defining Problem Types for Digest Fields
https://tus.github.io/draft-digest-fields-problem-types/draft-kleidl-digest-fields-problem-types.html
Other
1 stars 1 forks source link

Supported-algorthms duplicates want- response header? #2

Closed LPardue closed 4 months ago

LPardue commented 4 months ago

You say

A server MAY use this problem type when responding to a request, whose integrity or integrity preference fields reference a hashing algorithm that the server can not or does not want to support for this request, and if the server wants to indicate this problem to the sender.

From https://httpwg.org/specs/rfc9530.html#want-fields

If Want-Content-Digest or Want-Repr-Digest are used in a response, it indicates that the server would like the client to provide the respective Integrity field on future requests.

The Want- headers are a preference list of algorithms, It seems like Supported-algorthms duplicates the capability, which is not ideal. The unsupported-algorithm field is still usefule, since it might not be clear what algorithm specificall failed (imagine a request that contained multiple integrity fields with different algorithms and the application mandated that all of them must validate).

Acconut commented 4 months ago

Right, problem types gave me the ability to define additional members and I couldn't hold myself back from using it. Thanks!