Skip to content
master
Go to file
Code

Latest commit

From https://tus.io/protocols/resumable-upload.html#options
> A successful response indicated by the `204 No Content` or `200 OK` status MUST contain the `Tus-Version` header. It MAY include the `Tus-Extension` and `Tus-Max-Size` headers.
>
> The Client SHOULD NOT include the `Tus-Resumable` header in the request and the Server MUST ignore the header.

From https://tus.io/protocols/resumable-upload.html#tus-resumable
> The `Tus-Resumable` header MUST be included in every request and response except for `OPTIONS` requests. The value MUST be the version of the protocol used by the Client or the Server.
>
> If the version specified by the Client is not supported by the Server, it MUST respond with the `412 Precondition Failed` status and MUST include the `Tus-Version` header into the response. In addition, the Server MUST NOT process the request.

So we should omit the `Tus-Resumable` header from the OPTIONS request and clarify the example
5646c29

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 
 
 

README.md

tus resumable upload protocol

The protocol is in the protocol.md file.

It is rendered as HTML via Jekyll/Kramdown by the tus.io repository (type make preview there).

License

Licensed under the MIT license, see LICENSE.txt.

Copyright (c) 2013-2016 Transloadit Ltd and Contributors.

You can’t perform that action at this time.