Skip to content

Add optional Content-Location response header #159

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

Open
nigoroll wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add optional Content-Location response header #159

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
10 changes: 10 additions & 0 deletions protocol.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -141,6 +141,7 @@ Tus-Resumable: 1.0.0
HTTP/1.1 204 No Content
Tus-Resumable: 1.0.0
Upload-Offset: 100
Content-Location: https://tus.example.org/storage/d41d8cd98f00b204e9800998ecf8427e
```

### Headers
Expand Down Expand Up @@ -191,6 +192,15 @@ interpreted as the request's method by the Server, if the header is presented.
The actual method of the request MUST be ignored. The Client SHOULD use this
header if its environment does not support the PATCH or DELETE methods.

#### Content-Location

The Server MAY send a `Content-Location` header with any response once
the upload is complete (`Upload-Offset` == `Upload-Length`) to
optionally indicate to the Client a new location of the upload.

See [RFC 7231 Section
3.1.4.2](https://httpwg.org/specs/rfc7231.html#header.content-location).

### Requests

#### HEAD
Expand Down