Skip to content

Resumable uploads are HTTP version independent #202

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 26, 2025
Merged

Resumable uploads are HTTP version independent #202

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 5 additions & 8 deletions protocol.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,9 +70,9 @@ implementations (open source or commercial) if you'd like to be listed on the

## Abstract

The protocol provides a mechanism for resumable file uploads via HTTP/1.1 ([RFC
7230](https://tools.ietf.org/html/rfc7230)) and HTTP/2 ([RFC
7540](https://tools.ietf.org/html/rfc7540)).
The protocol provides a mechanism for resumable file uploads via HTTP ([RFC
9110](https://www.rfc-editor.org/rfc/rfc9110.html)). The protocol does not depend
on specific versions of HTTP.

## Notation

Expand Down Expand Up @@ -486,7 +486,7 @@ The latter one SHOULD be used if the Server is keeping track of expired uploads.
In both cases the Client SHOULD start a new upload.

The value of the `Upload-Expires` header MUST be in
[RFC 7231](https://tools.ietf.org/html/rfc7231#section-7.1.1.1) datetime format.
[RFC 9110](https://www.rfc-editor.org/rfc/rfc9110.html#name-date-time-formats) datetime format.

### Checksum

Expand Down Expand Up @@ -516,10 +516,7 @@ If the hash cannot be calculated at the beginning of the upload, it MAY be
included as a trailer. If the Server can handle trailers, this behavior MUST be
announced by adding `checksum-trailer` to the `Tus-Extension` header.
Trailers, also known as trailing headers, are headers which are sent after the
request's body has been transmitted already. Following
[RFC 7230](https://tools.ietf.org/html/rfc7230#section-4.1.2) they
MUST be announced using the `Trailer` header and are only allowed in chunked
transfers.
request's body has been transmitted already.

#### Headers

Expand Down
Loading