Tusd protocol for uploading to our servers
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Headers
| Headers params | Type | Description |
|---|---|---|
| Tus-Resumable | String | The Tus-Resumable header MUST be included in every request and response with value 1.0.0 |
| Upload-Length | Number | The Upload-Length header indicates the size of the entire upload in bytes. |
| Content-Type | String | application/offset+octet-stream |
| Upload-Metadata | String | 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. In these cases, the space, which would normally separate the key and the value, MAY be left out. Possible values:
|
Usage example available in our github
Uploader URLYou must notify the endpoint URL here is different from the other ones. This is because you're interacting with the upload server. It's important to notice this because we have many servers across the globe. The list Uploader Servers must be verified.
Please check tus protocol documentation.