search

ioggstream / draft-polli-resource-digests-http

THIS REPO WAS MOVED TO https://github.com/httpwg/http-extensions/
https://httpwg.org/http-extensions/draft-ietf-httpbis-digest-headers.html
Other
0 stars 1 forks source link

Explicitly reference content-type and content-encoding in the proposal introduction. #10

Closed ioggstream closed 5 years ago

ioggstream commented 5 years ago

This PR

Explicitly reference content-type and content-encoding in the proposal introduction.

@LPardue does it sound better? Actuallly the method's too impacts on resource representation (eg. HEAD vs GET). Should we state it here too?

LPardue commented 5 years ago

how about this wording?

The value of `Digest` is calculated on selected representation, which is tied to the value contained in any `Content-encoding` or `Content-type` header fields. Therefore, a given resource may have multiple different digest values.
ioggstream commented 5 years ago

@LPardue Question:

1- does selected representation identify only responses values tied to the Accept-* headers and content-negotiation? 2- does selected representation identify requests too (eg. where the selection is not actually negotiated)?

In the second case, your wordings is fine.