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
improve message abstraction to reflect semantics after message is parsed #557
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is also related to #294 |
reschke
approved these changes
Dec 3, 2020
mnot
reviewed
Dec 4, 2020
mnot
reviewed
Dec 4, 2020
mnot
requested changes
Dec 4, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a couple of notes, otherwise looks good.
Co-authored-by: Mark Nottingham <mnot@mnot.net>
mnot
approved these changes
Dec 5, 2020
reschke
approved these changes
Dec 5, 2020
triple-underscore
added a commit
to triple-underscore/triple-underscore.github.io
that referenced
this pull request
Dec 11, 2020
remove old organization intro text and update headings (editorial) editorial semantics httpwg/http-core#599 rearrange content negotiation so that all fields are at end editorial semantics httpwg/http-core#591 improve abstract editorial semantics httpwg/http-core#590 Reschke 571 httpwg/http-core#597 clarify that "no reason phrase" is fine as well (fixes # 571) editorial semantics httpwg/http-core#594 move method ABNF one paragraph down (fixes # 560) editorial semantics httpwg/http-core#596 fix an off-by-one bug about how many chars to consider when checking for etags (fixes # 570) semantics httpwg/http-core#595 Make TLS ref normative (fixes # 589) semantics httpwg/http-core#592 clarify that "no reason phrase" is fine as well (fixes # 571) editorial semantics httpwg/http-core#593 clarify the payload in 200 (OK) editorial semantics httpwg/http-core#576 simplify security consideration on confidentiality of credentials editorial semantics httpwg/http-core#587 update references to other security considerations editorial semantics httpwg/http-core#588 remove mention of "Warning" header field (fixes # 573) editorial semantics httpwg/http-core#577 add :authority pseudo-header to Host discussion and make section applicable to both semantics httpwg/http-core#575 note that HTTP/2 uses something other than `Host` httpwg/http-core#513 consistent indentation of "Notes" (fixes # 564) caching editorial semantics httpwg/http-core#569 improve message abstraction to reflect semantics after message is parsed httpwg/http-core#557 use payload or payload data for semantics instead of body or body data httpwg/http-core#555 semantics: remove surplus tables repeating field names (fixes # 562) editorial semantics httpwg/http-core#563 use proper field terminology when discussing trailer processing (fixes # 583) editorial semantics httpwg/http-core#558 define the Message Abstraction as an ADT rather than as a message httpwg/http-core#546 move the definition sections for Fields and Field Values up … httpwg/http-core#554 "canonical root URI" -> "origin" (fixes # 542) editorial semantics httpwg/http-core#552 move protocol version section up to conformance httpwg/http-core#551 remove table with validators (fixes # 537) editorial semantics httpwg/http-core#549 Remove obsolete note about a change in "Expect" syntax (fixes # 547) editorial semantics httpwg/http-core#548 Refine text about application caches httpwg/http-core#545 cleanup prior # 510 resolution to reduce nesting, fix punctuation, spelling httpwg/http-core#541 Say a bit more about PUT handling httpwg/http-core#535
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #556