| Table of Contents |
|---|
...
The mechanism that applications use to communicate with Swarm is a simple, text-based protocol based on HTTP. Known as the Simple Content Storage Protocol (SCSP), its methods and syntax are a proper subset of the HTTP/1.1 standard.
...
SCSP Method | HTTP Method | RFC 7231 Section |
|---|---|---|
GET | 4.3.1 | |
HEAD | 4.3.2 | |
POST | 4.3.3 | |
PUT | 4.3.4 | |
DELETE | 4.3.5 | |
n/a |
| 4.3.6 |
n/a |
| 4.3.7 |
n/a |
| 4.3.8 |
...
Most HTTP communication is initiated by a client application and consists of a request to be applied to an object on a Swarm server. In the simplest case, this is done using a single connection between the client application and the Swarm server. Being HTTP-based, SCSP protocol consists of HTTP requests and responses:
- Requests are generated by a Swarm client (that is, any HTTP/1.1 client), with these components:
- Request method, with URI and protocol version
- Case-insensitive query arguments
- Required and optional headers
- Responses are generated by one or more nodes in a storage cluster, with these components:
- Status line, with the message's protocol version and a success or error code
- MIME-like message, with server information, entity metadata, and possible entity-body content
See the HTTP/1.1 specification for the semantics and nuances of HTTP.
...