| Info |
|---|
New SENDAs of Swarm 11.2, SCSP SEND has been expanded to support all feed types and to use the new replication (PUSH) method. For backwards compatibility, the following legacy behavior of SEND is still supported. If a SEND request is missing the new required query arguments, then the behavior described here is in force. (v11.2) |
The SCSP SEND method applies to both named and unnamed objects. The SEND request allows explicit transmission of a single object from a source cluster to a remote one, such as for keeping two clusters immediately synchronized. This feature is best used with a replication feed, which acts as a catch-up mechanism if the intracluster network is down or the SEND command should fail.
...
The request returns information about that request in the body of the response. SEND behaves operates like a HEAD request, with the headers of the response resembling that of a HEAD request.
| Info |
|---|
ImportantThe SEND response is chunked transfer encoded, so the client of the SEND request must be prepared for chunked transfer encoding. The response body may contain additional leading newlines sent incrementally, which keeps the connection open in long requests. |
The most common HTTP response codes are these:
201 - the object has been transferred successfully
409 - the object already exists in the destination cluster
...