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.

Sign up for GitHub

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

Don't rely on the HTTP/1.1 Messaging specification to define "message" #344

Merged
merged 2 commits into from
Apr 27, 2020
Merged

Don't rely on the HTTP/1.1 Messaging specification to define "message" #344

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ce0b381
Don't rely on the HTTP/1.1 Messaging specification to define "message"
mnot Mar 20, 2020
d5c266e
Merge branch 'master' into mnot-311
mnot Apr 27, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions draft-ietf-httpbis-semantics-latest.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -383,8 +383,7 @@
<iref primary="true" item="connection"/>
<t>
HTTP is a stateless request/response protocol that operates by exchanging
<x:dfn>messages</x:dfn> (<xref target="http.message"/>) across a reliable
transport- or session-layer
<x:dfn>messages</x:dfn> across a reliable transport- or session-layer
"<x:dfn>connection</x:dfn>" (<xref target="connection.management"/>).
An HTTP "<x:dfn>client</x:dfn>" is a program that establishes a connection
to a server for the purpose of sending one or more HTTP requests.
Expand Down Expand Up @@ -12461,6 +12460,7 @@ Content-Encoding: gzip
<li>In <xref target="content.negotiation"/>, introduce the concept of request payload negotiation (<xref target="request.payload.negotiation"/>) and define for <x:ref>Accept-Encoding</x:ref> (<eref target="https://github.com/httpwg/http-core/issues/119"/>)</li>
<li>In <xref target="CONNECT"/>, correct language about what is forwarded (<eref target="https://github.com/httpwg/http-core/issues/170"/>)</li>
<li>In <xref target="considerations.for.new.header.fields"/> and <xref target="considerations.for.new.status.codes"/>, describe how extensions should consider scope of applicability (<eref target="https://github.com/httpwg/http-core/issues/265"/>)</li>
<li>In <xref target="operation"/>, don't rely on the HTTP/1.1 Messaging specification to define "message" (<eref target="https://github.com/httpwg/http-core/issues/311"/>)</li>
</ul>
</section>
</section>
Expand Down