chore(http): Refresh headers docs (d-k)

[bsmth]

Description

This PR refreshes a few HTTP headers pages.

common changes:

• Improve See also
• Capitalize Yes/No in properties table
• Normalize The HTTP **`Header-Name`** (request|response) header in first sentence
• Add status text to HTTPStatus macros, e.g. {{HTTPStatus("406", "406 Not Acceptable")}}
• Remove improper use of quotes in and around code
• Avoid escaping angle brackets in directive names in favor of backticks:

- \<directive>
+ `<directive>`

Motivation

Keeping content up-to-date, fixing formatting, unifying writing conventions

Related pull requests:

• chore(http): Refresh some headers pages (~a-c) #36038

[github-actions]

Preview URLs (22 pages)

• /en-US/docs/Glossary/Forbidden_header_name
• /en-US/docs/Web/HTTP/Headers/DNT
• /en-US/docs/Web/HTTP/Headers/DPR
• /en-US/docs/Web/HTTP/Headers/Date
• /en-US/docs/Web/HTTP/Headers/Device-Memory
• /en-US/docs/Web/HTTP/Headers/Digest
• /en-US/docs/Web/HTTP/Headers/Downlink
• /en-US/docs/Web/HTTP/Headers/ECT
• /en-US/docs/Web/HTTP/Headers/ETag
• /en-US/docs/Web/HTTP/Headers/Early-Data
• /en-US/docs/Web/HTTP/Headers/Expect-CT
• /en-US/docs/Web/HTTP/Headers/Expect
• /en-US/docs/Web/HTTP/Headers/Expires
• /en-US/docs/Web/HTTP/Headers/Forwarded
• /en-US/docs/Web/HTTP/Headers/From
• /en-US/docs/Web/HTTP/Headers/Host
• /en-US/docs/Web/HTTP/Headers/If-Match
• /en-US/docs/Web/HTTP/Headers/If-Modified-Since
• /en-US/docs/Web/HTTP/Headers/If-None-Match
• /en-US/docs/Web/HTTP/Headers/If-Range
• /en-US/docs/Web/HTTP/Headers/If-Unmodified-Since
• /en-US/docs/Web/HTTP/Headers/Keep-Alive

Flaws (1)

Note! 21 documents with no flaws that don't need to be listed. 🎉

URL: /en-US/docs/Web/HTTP/Headers/Digest
Title: Digest
Flaw count: 1

• bad_bcd_queries:
  • No BCD data for query: http.headers.Digest

External URLs (7)

URL: /en-US/docs/Web/HTTP/Headers/Expect-CT
Title: Expect-CT

• https://chromestatus.com/feature/6244547273687040 (1 time) (Note! This may be a new URL 👀)

---

URL: /en-US/docs/Web/HTTP/Headers/Keep-Alive
Title: Keep-Alive

• https://httpwg.org/specs/rfc9113.html (1 time) (Note! This may be a new URL 👀)
• https://httpwg.org/specs/rfc9114.html (1 time) (Note! This may be a new URL 👀)

---

URL: /en-US/docs/Web/HTTP/Headers/DPR
Title: DPR

• https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-client-hints-07 (1 time) (Note! This may be a new URL 👀)
• https://developer.chrome.com/docs/privacy-security/user-agent-client-hints (1 time) (Note! This may be a new URL 👀)
• https://wicg.github.io/responsive-image-client-hints/ (1 time) (Note! This may be a new URL 👀)

---

URL: /en-US/docs/Web/HTTP/Headers/If-None-Match
Title: If-None-Match

• https://www.w3.org/1999/04/Editing/ (1 time) (Note! This may be a new URL 👀)

(comment last updated: 2024-10-29 17:06:07)

[github-actions]

This pull request has merge conflicts that must be resolved before it can be merged.

[hamishwillee]

Again, I like this form ...

Suggested change

	The HTTP **`Digest`** header provides the recipient with a {{Glossary("digest")}} of the {{HTTPHeader("Content-Encoding")}}-encoded _selected representation_.
	The HTTP **`Digest`** {{Glossary("Request header","request")}} and {{Glossary("Response header","response")}} header provides the recipient with a {{Glossary("digest")}} of the {{HTTPHeader("Content-Encoding")}}-encoded _selected representation_.

[hamishwillee]

PS Also check https://developer.mozilla.org/en-US/docs/MDN/Writing_guidelines/Page_structures/Page_types/HTTP_header_page_template to make sure it matches all this work you are doing!

[hamishwillee]

Note that the change you have made puts all the content up the top. I am happy with that, but in some case we might have too much information. So for the template I'd suggest that if the intro goes over the fold the author is allowed to add a separate section "Description" after the directive and before the direction, moving most of the content to that section.

That somewhat mirrors what Web APIs do.

[bsmth]

add a separate section "Description" after the directive and before the direction

I don't follow this one 😄, where do you think "Description" should go?

[hamishwillee]

So in Web APIs this appears after syntax sections, before Examples. The template hints that you have a short introductory sentence and then all the detail in the description. I don't particularly like that and try to avoid a description section if I can keep the text up the top succint.

So this pattern for HTTP would be:

Open to discussion. We don't have to do this, we just need to make sure that all this work you're doing is captured.

[hamishwillee]

I wonder if this warning should perhaps live up the top with the other headers?

[bsmth]

I think we can put it up top, but we're getting pretty strong banner overload on this page now:

[hamishwillee]

Absolutely correct. I don't think that matters because this is deprecated and we don't really want people to read it anyway :-).

That said, hopefully Ruth will eventually get the proposal for banners sorted out and implemented.

[hamishwillee]

FWIW I don't really "get" this, but I am pretty sure that it doesn't matter - this is sufficient for most readers.

[bsmth]

Maybe we can add some details to this page: https://aws.github.io/s2n-tls/usage-guide/ch14-early-data.html

[bsmth]

I also noticed there's no See also section here

[hamishwillee]

OK. I don't feel very strongly either way. It feels like the kind of thing only a deep dark expert would need, and they would read the spec.

[bsmth]

Missing a See also section on this page