Recover the authoritative durable upload offset
HEAD/api/v1/uploads/:upload_id
Requires documents.create, Tus-Resumable 1.0.0, and the authenticated intake scope that owns the upload. An accepted session also requires current documents.read permission and access to its document. Returns durable offset, declared length, and expiry; unknown, cross-scope, canceled, expired, and unreadable accepted sessions return 404.
Request
Responses
- 204
- 401
- 404
- 412
- 421
- 503
Upload-Offset, Upload-Length, and Upload-Expires describe the session
Response Headers
TUS protocol version 1.0.0
HTTP-date after which the session expires
Declared total byte length
Current durable byte offset
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The opaque credential is absent, ambiguous, malformed, expired, revoked, or invalid
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The resource is unknown or outside the authenticated household scope
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The strong revision precondition is stale
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
The request authority or direct peer is outside the configured Jiandu ingress boundary
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.
A required core dependency is unavailable; retry with bounded backoff
Response Headers
Opaque request correlation identifier. ProblemDetails.requestId carries the same value on JSON failures.