TUS

TUS POST /api/upload/tus

Changed on

TUS protocol POST handler for /api/upload/tus

post/api/upload/tus

Request

  • Base URL: / (relative, and the document was published on a file host, not at the API’s origin)
  • URL: /api/upload/tus
  • Auth: none declared. Required headers: Tus-Resumable, Upload-Length

Headers

Content-Lengthinteger

Must be 0 for creation extension. May be a positive number for Creation With Upload extension.

Tus-Resumableobject required
Upload-Checksumobject

Added by the Creation With Upload Extension in combination with the checksum extension. Checksum of the included data.

Upload-Concatstring

Added by the Concatenation extension. Indicates whether the upload is either a partial or final upload.

Upload-Defer-Lengthinteger

Added by the Creation Defer Length extension. Indicates that the size of the upload is not known currently.

Upload-Lengthobject required
Upload-Metadatastring

Added by the Creation extension. The Upload-Metadata request and response header MUST consist of one or more comma-separated key-value pairs. The key and value MUST be separated by a space. The key MUST NOT contain spaces and commas and MUST NOT be empty. The key SHOULD be ASCII encoded and the value MUST be Base64 encoded. All keys MUST be unique. The value MAY be empty. In these cases, the space, which would normally separate the key and the value, MAY be left out. Since metadata can contain arbitrary binary values, Servers SHOULD carefully validate metadata values or sanitize them before using them as header values to avoid header smuggling.

Upload-Offsetobject

Added by the Creation With Upload Extension. Indicates the offset of the included data.

Response

Success

Changes

    • breaking

      the response's property type changed from string to object for status

    • info

      added the optional property / to the response with the status

    • info

      added the required property / to the response with the status

    • info

      endpoint added