feat(http): Update some mentions of "payload" -> "content"#35335
feat(http): Update some mentions of "payload" -> "content"#35335hamishwillee merged 9 commits intomdn:mainfrom
Conversation
Preview URLs (19 pages)
Flaws (49)Note! 4 documents with no flaws that don't need to be listed. 🎉 URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
URL:
External URLs (4)URL:
URL:
(comment last updated: 2024-08-28 09:34:25) |
|
@hamishwillee the other PR was... trashed from merge conflicts and git hijinks. I incorporated all of your comments, with some other clarifications that I hope make it clearer. Because we don't see "content headers" defined in later specs, I'm not sure how useful this page is, but at least we shouldn't really be talking about "payload headers" anymore. No rush on this, btw! 🙏🏻 |
|
I think I was perhaps a bit picky but I found this very hard to review - mostly because until I got near the end I was still unclear on exactly how content and representation headers differ. Now I know :-) Thank you. |
Thanks Hamish! It becomes clearer why "payload headers" are dropped in later RFCs and we're left with "representation headers" for metadata, then everything else is either a request or a response header. I think that's less confusing. |
Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
Co-authored-by: Hamish Willee <hamishwillee@gmail.com>
hamishwillee
left a comment
There was a problem hiding this comment.
Thanks very much @bsmth - LGTM.
Description
Replaces #35063 because of git hijinks.
This is a maintenance PR part of work to refresh HTTP docs.
Fixes #20741 which looks like a simple change, but it's trickier because we have to be more abstract to encompass HTTP/1.1 -> HTTP/3 concepts.
Changes:
Payload_body->HTTP_ContentPayload_header->Content_headerMotivation
Keeping content up-to-date and useful.
Related issues and pull requests: