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
It looks like "request" and "response" are defined in https://httpwg.org/http-core/draft-ietf-httpbis-semantics-latest.html#operation as kinds of "messages", and then "messages" are defined in the same section by reference to https://httpwg.org/http-core/draft-ietf-httpbis-messaging-latest.html#http.message ... which only applies to HTTP/1.1. I think these are intended to be version-independent concepts, so they need a version-independent definition.
The text was updated successfully, but these errors were encountered:
Each version defines how a message is transferred, but I agree that the concept of what a message is needs to be defined independently.
Sorry, something went wrong.
Don't rely on the HTTP/1.1 Messaging specification to define "message"
ce0b381
Fixes #311
I took the most minimal approach. I could also imaging rearranging things so that there's a top-level section "messages" to define these things more prominently, but that can be done editorially if we think it's worthwhile.
mnot
Successfully merging a pull request may close this issue.
It looks like "request" and "response" are defined in https://httpwg.org/http-core/draft-ietf-httpbis-semantics-latest.html#operation as kinds of "messages", and then "messages" are defined in the same section by reference to https://httpwg.org/http-core/draft-ietf-httpbis-messaging-latest.html#http.message ... which only applies to HTTP/1.1. I think these are intended to be version-independent concepts, so they need a version-independent definition.
The text was updated successfully, but these errors were encountered: