Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / tus/tus-resumable-upload-protocol issues and pull requests
#50 - add note about 100 Continue
Pull Request -
State: closed - Opened by Acconut almost 10 years ago
- 2 comments
#49 - add streams extension
Pull Request -
State: closed - Opened by Acconut almost 10 years ago
- 7 comments
#49 - add streams extension
Pull Request -
State: closed - Opened by Acconut almost 10 years ago
- 7 comments
#48 - add protocol discovery
Pull Request -
State: closed - Opened by Acconut almost 10 years ago
#48 - add protocol discovery
Pull Request -
State: closed - Opened by Acconut almost 10 years ago
#47 - add section about metadata to file creation extension
Pull Request -
State: closed - Opened by Acconut almost 10 years ago
#47 - add section about metadata to file creation extension
Pull Request -
State: closed - Opened by Acconut almost 10 years ago
#46 - add retry extension
Pull Request -
State: closed - Opened by Acconut almost 10 years ago
#46 - add retry extension
Pull Request -
State: closed - Opened by Acconut almost 10 years ago
#45 - add retry extension
Pull Request -
State: closed - Opened by Acconut almost 10 years ago
- 1 comment
Labels: extension
#45 - add retry extension
Pull Request -
State: closed - Opened by Acconut almost 10 years ago
- 1 comment
Labels: extension
#44 - URLs and authentication are not part of the protocol
Pull Request -
State: closed - Opened by Acconut almost 10 years ago
Labels: core
#44 - URLs and authentication are not part of the protocol
Pull Request -
State: closed - Opened by Acconut almost 10 years ago
Labels: core
#43 - How to properly use Content-Type
Issue -
State: closed - Opened by qsorix almost 10 years ago
- 3 comments
Labels: question
#43 - How to properly use Content-Type
Issue -
State: closed - Opened by qsorix almost 10 years ago
- 3 comments
Labels: question
#42 - Use 204 No Content instead of 200 Ok in PATCH and HEAD request
Pull Request -
State: closed - Opened by Acconut almost 10 years ago
#42 - Use 204 No Content instead of 200 Ok in PATCH and HEAD request
Pull Request -
State: closed - Opened by Acconut almost 10 years ago
#41 - 204 No content
Pull Request -
State: closed - Opened by Acconut almost 10 years ago
#41 - 204 No content
Pull Request -
State: closed - Opened by Acconut almost 10 years ago
#40 - add upload expiration extension
Pull Request -
State: closed - Opened by Acconut almost 10 years ago
- 10 comments
Labels: extension
#40 - add upload expiration extension
Pull Request -
State: closed - Opened by Acconut almost 10 years ago
- 10 comments
Labels: extension
#39 - Describe how to provide metada
Issue -
State: closed - Opened by qsorix about 10 years ago
- 14 comments
Labels: enhancement, extension
#39 - Describe how to provide metada
Issue -
State: closed - Opened by qsorix about 10 years ago
- 14 comments
Labels: enhancement, extension
#38 - Where to specify filename
Issue -
State: closed - Opened by MarkMurphy over 10 years ago
- 18 comments
Labels: question
#38 - Where to specify filename
Issue -
State: closed - Opened by MarkMurphy over 10 years ago
- 18 comments
Labels: question
#37 - [Core] There's no way to find out if transfer is completed on server side
Issue -
State: closed - Opened by lleoha over 10 years ago
- 1 comment
Labels: question
#37 - [Core] There's no way to find out if transfer is completed on server side
Issue -
State: closed - Opened by lleoha over 10 years ago
- 1 comment
Labels: question
#36 - Fear of creating extra requests?
Issue -
State: closed - Opened by tino over 10 years ago
- 4 comments
#35 - Upload expiration
Issue -
State: closed - Opened by MarkMurphy over 10 years ago
- 28 comments
Labels: extension
#34 - Web site uses protocol version 0.2.1 instead of 0.2.2
Issue -
State: closed - Opened by ChristianUlbrich over 10 years ago
- 1 comment
#33 - Project status?
Issue -
State: closed - Opened by ChristianUlbrich over 10 years ago
- 30 comments
Labels: question
#32 - fixes tus/tus-resumable-upload-protocol#31
Pull Request -
State: closed - Opened by vayam almost 11 years ago
#31 - HEAD request with non-existent previous upload should return 404
Issue -
State: closed - Opened by vangheem almost 11 years ago
- 7 comments
#30 - Reduce implications of Location header field.
Issue -
State: closed - Opened by sheeep about 11 years ago
- 8 comments
#29 - Allow protocol discovery between client and server.
Issue -
State: closed - Opened by timemachine3030 over 11 years ago
- 21 comments
Labels: core
#28 - Standardize support for streaming uploads
Issue -
State: open - Opened by jonhoo over 11 years ago
- 32 comments
Labels: enhancement, extension
#27 - Do we need a separate request to create uploads?
Issue -
State: closed - Opened by technoweenie over 11 years ago
- 2 comments
#26 - Response to HEAD should use Content-Length, not Offset
Issue -
State: closed - Opened by jonhoo over 11 years ago
- 13 comments
#25 - The protocol SHOULD describe retry for clients :)
Issue -
State: closed - Opened by kvz over 11 years ago
- 11 comments
Labels: enhancement, extension
#24 - Describe large file chunking as a part of protocol
Issue -
State: closed - Opened by wronglink over 11 years ago
- 11 comments
Labels: question
#23 - Add Content-Type to PATCH example
Pull Request -
State: closed - Opened by vayam over 11 years ago
- 1 comment
#22 - Rename Final-Length to Entity-Length
Issue -
State: closed - Opened by felixge over 11 years ago
- 5 comments
#21 - Add Content-Type to PATCH request
Pull Request -
State: closed - Opened by vayam over 11 years ago
- 7 comments
#20 - Content-Type for PATCH
Issue -
State: closed - Opened by felixge over 11 years ago
- 1 comment
Labels: bug
#19 - Rename Final-Size -> Final-Length
Pull Request -
State: closed - Opened by vayam over 11 years ago
- 6 comments
#18 - Ressource allocation/timeout
Issue -
State: closed - Opened by radiospiel over 11 years ago
- 3 comments
#17 - 202 Accepted Response?
Issue -
State: closed - Opened by aranw over 11 years ago
- 3 comments
#16 - Support streams with unknown length?
Issue -
State: closed - Opened by felixge over 11 years ago
- 13 comments
Labels: enhancement, extension
#15 - Clarify that POST is an optional step
Issue -
State: closed - Opened by felixge over 11 years ago
- 4 comments
Labels: bug
#14 - PATCH vs PUT
Issue -
State: closed - Opened by felixge over 11 years ago
- 48 comments
Labels: bug, core
#13 - Define behavior for GET on incomplete uploads
Issue -
State: closed - Opened by biasedbit over 11 years ago
- 16 comments
#12 - Consider using 204 No Content
Issue -
State: closed - Opened by felixge over 11 years ago
- 3 comments
Labels: bug, core
#11 - Clarify that url does not have to be fixed
Issue -
State: closed - Opened by felixge over 11 years ago
Labels: enhancement
#10 - Mention authentication in protocol
Issue -
State: closed - Opened by felixge over 11 years ago
Labels: enhancement
#9 - 100-Continue Research
Issue -
State: closed - Opened by felixge over 11 years ago
- 10 comments
Labels: enhancement
#8 - [duplicate] Optional checksumming
Issue -
State: closed - Opened by cybic over 11 years ago
- 1 comment
#7 - Checksum Support (MD5,CRC32,SHA1,etc.)
Issue -
State: closed - Opened by sandfox over 11 years ago
- 75 comments
Labels: enhancement, extension
#6 - make example urls in protocol work
Issue -
State: closed - Opened by felixge over 11 years ago
- 1 comment
Labels: enhancement
#5 - Describe limits for upload size
Issue -
State: closed - Opened by biasedbit over 11 years ago
- 5 comments
Labels: enhancement
#4 - Add S3 Multipart Uploads to Prior art
Issue -
State: closed - Opened by biasedbit over 11 years ago
- 3 comments
#3 - Define behaviour when uploading non-contiguous chunks
Issue -
State: closed - Opened by sandfox over 11 years ago
- 5 comments
Labels: enhancement, extension
#2 - "Range" vs. "Content-Range"
Issue -
State: closed - Opened by awendt over 11 years ago
- 8 comments
Labels: bug, core
#1 - Rework language to use MUST, MAY, etc.
Issue -
State: closed - Opened by felixge over 11 years ago
- 1 comment
Labels: enhancement