Versions Compared

Old Version 8

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

Saved on

compared with

New Version 9

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

Saved on

Key

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

...

SCSP Method

HTTP Method

RFC 7231 Section

SCSP WRITE

POST

4.3.3

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 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)

WRITE for named objects

The existing object is overwritten with a new version if performing a WRITE of a named object that already 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 allows the client to omit the Expect: 100-continue header, sending all the content at once. The server reads and discards all data if it must respond with a redirect or error. Swarm logs a warning for WRITE messages that include more than 65536 bytes:

...