AtHeartEngineer/specs
1
0
Fork 0
mirror of https://github.com/vacp2p/specs.git synced 2026-01-08 23:08:09 -05:00
Code Issues Packages Projects Releases Wiki Activity

Formatting

Browse Source
This commit is contained in:
Marco Munizaga
2023-07-17 14:46:04 -07:00
parent db2b3b5492
commit 6319458d74
1 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
http/README.md
View File

@@ -27,13 +27,16 @@ As well as allowing application protocols to make use of HTTP intermediaries suc
- Peer ID Authentication – Authenticate your peer by their libp2p peer id.
- Peer discovery – Learn about a peer given their peer id.
## HTTP Transport vs HTTP Semantics
## HTTP Semantics vs HTTP Transport
HTTP is a bit of an overloaded term. This section aims to clarify what we’re talking about when we say “HTTP”.
*HTTP semantics* ([RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html)) is the stateless application-level protocol that you work with when writing HTTP apis (for example).
- *HTTP semantics* ([RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html)) is
the stateless application-level protocol that you work with when writing HTTP
apis (for example).
*HTTP transport* is the thing that takes your high level request/response defined in terms of HTTP semantics and encodes it and sends it over the wire.
- *HTTP transport* is the thing that takes your high level request/response
defined in terms of HTTP semantics and encodes it and sends it over the wire.
When this document says *HTTP* it is generally referring to *HTTP semantics*.