chore(http): Refresh headers r-s#36590
Conversation
|
Aware of this. Hope to get to it next week. |
Thanks, Hamish. There's no rush on the HTTP PRs at the moment. |
| In contrast to earlier drafts of the specification, the standard-base64-encoded digest bytes are wrapped in colons (`:`, ASCII 0x3A) as part of the [dictionary syntax](https://www.rfc-editor.org/rfc/rfc8941#name-byte-sequences). | ||
|
|
||
| The registered insecure digest algorithms are: `md5`, `sha` (SHA-1), `unixsum`, `unixcksum`, `adler` (ADLER32) and `crc32c`. | ||
| ### Usage notes |
There was a problem hiding this comment.
We have a mix of "Usage notes" and "Description" sections, related to the previous PR. It would be good to choose a convention for that.
There was a problem hiding this comment.
Yes. I vote description for broader consistency across reference docs of other types.
Not necessarily and easy change though - these usage notes are in some cases just notes. For example here you couldn't just change the heading and expect it to "work" as a fix.
There was a problem hiding this comment.
(I removed the section title in this case)
| {{HTTPSidebar}} | ||
|
|
||
| The **`Repr-Digest`** response or request header provides a {{Glossary("digest")}} of the [selected representation](https://www.rfc-editor.org/rfc/rfc9110#section-6.4) of the target resource. It is invariant under e.g., {{HTTPHeader("Content-Encoding")}} or {{HTTPHeader("Content-Range")}}, which do affect the {{HTTPHeader("Content-Digest")}}. Furthermore, [Content Negotiation](/en-US/docs/Web/HTTP/Content_negotiation) can result in different selected representations with different representation digests. | ||
| The HTTP **`Repr-Digest`** {{Glossary("Request header", "request")}} and {{Glossary("Response header", "response header")}} provides a {{Glossary("digest")}} of the [selected representation](https://www.rfc-editor.org/rfc/rfc9110#section-6.4) of the target resource. |
There was a problem hiding this comment.
We should use a glossary entry instead of RFC link for selected representation.
files/en-us/web/http/headers/sec-ch-prefers-reduced-transparency/index.md
Outdated
Show resolved
Hide resolved
hamishwillee
left a comment
There was a problem hiding this comment.
@bsmth Look great. Just a few suggestions on the early ones.
Thanks a lot, I'll take a look shortly 🙏🏻 |
Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
|
Thanks, Hamish. I think this is mostly done, ready for another look when you have time. I'm going to have a look at BCD for the WebSocket pages 👀 |
There was a problem hiding this comment.
@bsmth The changes you made all look good, so I am going to merge. Note that I only looked at those changes, but I was happy with the rest last time round.
Thanks very much. Nearly there!
|
Thanks a lot! |
* origin/xss-guide: (284 commits) Add information on default entryPoint property values (mdn#36633) Bump husky from 9.1.6 to 9.1.7 (mdn#36863) fix(performance): Typo '50ms seconds' (mdn#36861) Add spec_url & add note for bcd for `<frequency>` and `<frequency-percentage>` (mdn#36848) addresses 36583: summary icon styles (mdn#36691) Remove "simple" part 3: change to "basic" (mdn#36762) the default option of a select (mdn#36658) docs(css): Add support for `<string>` in `syntax` descriptor of @Property at-rule (mdn#36655) Fix parameter syntax for `Navigation.updateCurrentEntry()` (mdn#36852) Update CSP source expression reference (mdn#36792) chore(http): Refresh headers docs (d-k) (mdn#36075) chore(http): Refresh headers r-s (mdn#36590) Updated index.md (mdn#36845) fix : wrong method name (mdn#36843) Remove all redirects to other locales (mdn#36811) fix typos (mdn#36837) docs: update Accept-Charset status (mdn#36822) updateSelection: make more intuitive (mdn#36834) updateText: Remove false information (mdn#36832) DOMRect instance properties (mdn#36704) ...
Description
This PR refreshes a few HTTP headers pages.
common changes:
The HTTP **`Header-Name`** (request|response) headerin first sentence{{HTTPStatus("406", "406 Not Acceptable")}}Motivation
Keeping content up-to-date, fixing formatting, unifying writing conventions
TODO: