-
The purpose of this ticket is to summarize the way all clients can and should use TUS to upload big files to oCIS for the MVP/GA version of oCIS. This is a cross-component topic between oCIS and all c…
-
## PLIP (Plone Improvement Proposal)
## Abstract
This PLIP has three aims (and could be separated if desired)
- Implement TUS in volto for "contents > upload" with a UI similar to quanta design (…
-
Like javascript-based clients, let's use the tus.io protocol for the client-py.
It has the following advantages:
* All the advantages of tus.io protocol such as resuming uploads
* More accurate pro…
-
**Target Jetty version(s)**
jetty-12
**Enhancement Description**
Resumable upload support needs to be monitored to see if we need to support it in multipart upload (plus the new 104 response code…
gregw updated
2 months ago
-
I have tried this, but currently the file gets handed to the storage handler (Azure in my case), which tries to upload it.
Subsequently this fails and the tus client request gets rejected.
So I wa…
-
tus 1.0 is just around the corner. I would be pleased to see this implementation being updated to support the next version. Most updates are outside the core so only minimal changes are required to ma…
-
Right now, the specification says following about the Tus-Resumable header:
> The Tus-Resumable header MUST be included in every request and response except for OPTIONS requests. The value MUST be …
-
For HTTP responses, [Content-Type](https://httpwg.org/specs/rfc7231.html#header.content-type) is de-facto required to avoid user-agents having to guess mime-types (the RFC says _SHOULD_ be generated).…
-
**Describe the bug**
If a remote resource is deferred and the server reports the "Upload-Defer-Length: 1" header,
tus-js-client is not able to upload against the resource without options.uploadLengt…
-
In https://tus.io/faq.html#how-do-i-scale-tus there is the annoying requirement:
> You only need to ensure that there is no parallel access to a single upload resource from multiple tus servers.
…