Versions Compared

Old Version 6

changes.mady.by.user Kyle Miller (Deactivated)

Saved on

compared with

New Version 7

changes.mady.by.user Kyle Miller (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

...

Info

Write for contexts

The Swarm setting scsp.requireExplicitContextCreate protects content-bearing objects from being created erroneously as contexts (buckets or domains). With this setting enabled, Swarm will does not create a context object unless it includes the required header: Content-type: application/castorcontext. (v9.1)

Info

S3 compatibility

The Swarm setting scsp.autoContentMD5Computation improves S3 compatibility by automating Content-MD5 hashing. the gencontentmd5 query argument or the deprecated Expect: Content-MD5 header does not need to be included on writes (although a separate Content-MD5 header may want to be supplied for content integrity checking). This setting is ignored wherever it is invalid, such as on a multipart initiate/complete or an EC APPEND. (v9.1)

...

  • Swarm WRITEs the named object if the named object does not exist.

  • Swarm responds with a an HTTP 412 Precondition Fail error if the named object exists.

...

Info

Exception

Although domains and buckets are named, Swarm processes all PUT requests on these objects as updates, regardless of the setting.

  • Swarm fails the request with a 400 Bad Request error if the putcreate=yes query argument is used on a domain or bucket.

  • Swarm silently ignores it and processes the request as an ordinary PUT if the scsp.allowPutCreate parameter is enabled.

Preventing overwriting: If-None-Match

...

  • Swarm WRITEs the named object if the named object does not exist.

  • Swarm responds with a an HTTP 412 Precondition Fail error if the named object exists.

Info

Note

Swarm returns a an HTTP 412 error on SCSP WRITE of named objects if the domain or bucket does not exist or cannot be loaded.

...

See Working with Large Objects.

Info

Note

Swarm returns a HTTP 503 Service Unavailable error if performing a WRITE of an object of more than 4 TB in size.

...

The Expect: 100-continue header tells the server that the client will wait waits after sending the header lines and before sending the content in the message body. The Swarm server can respond with a redirect or an error response.

  • The server returns a an HTTP 100 Continue response, telling the client to transmit the entity body if the server is ready to store the contents. The client needs to wait for a 100 Continue response from the server before proceeding to send the data.

  • The server sends a an HTTP 413 Request entity too large error response and closes the connection if the server is not ready.

...

Code Block
languageerl
Please use Expect: 100-continue for large amounts of data.

The cluster returns a an HTTP 507 Insufficient Storage error if any node in the cluster does not have enough space to write the object.

...