Skip to content
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.

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

Fix: #967. Clarify the _returned value_ expression. #969

Merged
merged 2 commits into from Nov 3, 2019

Conversation

ioggstream
Copy link
Contributor

This PR

Clarifies the "returned value" expression.

Fixes: #967

Copy link
Contributor

@LPardue LPardue left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. Longer term, I'd like to do an broad editorial sweep to tighten up document and this is an enabling step that I think this takes us most of the way there. I made some suggestions to move words around a bit.

draft-ietf-httpbis-digest-headers.md Show resolved Hide resolved
### Digest in both Request and Response. Field-values depends on representation metadata

The request contains a `Digest` header
calculated on the enclosed representation.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here I would highlight the Accept-Encoding header and then reword the next paragraph slightly e.g.

"It also includes an Accept-Encoding: br header field that advertises the client supports brotli encoding"

Comment on lines 601 to 604
The `Digest` field-value in the response is different
from the one of the request
because we used `Accept-Encoding` to selected another
representation respect to the sent one.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Then reword this as something like:

"The response includes a Content-Encoding:br that indicates the selected representation is brotli encoded. The Digest field-value is therefore different compared to the request.

@ioggstream ioggstream merged commit 4f96403 into master Nov 3, 2019
@ioggstream ioggstream deleted the ioggstream-967 branch November 3, 2019 11:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

"Digest can be used in requests too. Returned value depends on the representation metadata header fields."
2 participants