Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / remotestorage/spec issues and pull requests
#191 - Should 304/412 response take preference over 404?
Issue -
State: open - Opened by michielbdejong 8 months ago
- 5 comments
#190 - Public requests must also include 'public' in Cache-Control header (resolves #189)
Pull Request -
State: open - Opened by DougReeder 10 months ago
#189 - Cache-Control should also include 'public' for public document GET requests
Issue -
State: open - Opened by DougReeder 11 months ago
- 4 comments
#188 - remote-storage with orbit-db
Issue -
State: closed - Opened by ghost about 2 years ago
- 2 comments
#187 - Remove protocol versions from implementations, in part or entirely
Issue -
State: open - Opened by raucao about 2 years ago
- 4 comments
#186 - Version control in remote-storage
Issue -
State: closed - Opened by ghost about 2 years ago
- 2 comments
#185 - Clarifies description of folder listing
Pull Request -
State: closed - Opened by DougReeder over 2 years ago
#184 - Move wiki content to this repo?
Issue -
State: closed - Opened by rosano over 3 years ago
- 3 comments
#183 - Formally require OAuth client_id to match the origin of the redirect_uri
Issue -
State: open - Opened by raucao over 4 years ago
Labels: enhancement, security, clarity
#182 - Add @skddc as third author
Pull Request -
State: closed - Opened by michielbdejong over 4 years ago
- 3 comments
#181 - Case sensitivity of path/document names
Issue -
State: open - Opened by raucao almost 5 years ago
- 2 comments
Labels: question
#180 - GET requests to empty folders - clarify
Issue -
State: open - Opened by michielbdejong almost 5 years ago
- 1 comment
#179 - Put something on ontology URL
Issue -
State: open - Opened by michielbdejong almost 5 years ago
- 1 comment
#178 - unclear sentence
Issue -
State: open - Opened by michielbdejong almost 5 years ago
- 2 comments
#177 - Add CHANGELOG entries for version -13 and -14
Pull Request -
State: closed - Opened by galfert almost 5 years ago
#176 - Consider requiring PKCE
Issue -
State: open - Opened by michielbdejong over 5 years ago
- 4 comments
#175 - OAuth: Specify allowed schemes for redirect_uri parameter
Issue -
State: open - Opened by palant over 5 years ago
- 9 comments
#174 - OAuth: Specify a special redirect_uri for manual token copy&paste
Issue -
State: open - Opened by palant over 5 years ago
- 2 comments
#173 - Send `Last-Modified` in response to PUT
Issue -
State: open - Opened by sonnyp almost 6 years ago
#172 - Access-Control-Expose-Headers
Issue -
State: open - Opened by sonnyp almost 6 years ago
- 3 comments
Labels: enhancement, clarity
#171 - Write-only permission
Issue -
State: open - Opened by raucao almost 6 years ago
- 9 comments
Labels: enhancement
#170 - Move from Implicit Grant to PKCE
Issue -
State: open - Opened by rullzer about 6 years ago
- 4 comments
#169 - Explicitly disallow documents and folders with the same name
Issue -
State: closed - Opened by galfert over 6 years ago
#168 - Changelog is missing entries for -10 and -11
Issue -
State: closed - Opened by galfert over 6 years ago
#167 - Remove obsolete OWA manifest language
Issue -
State: open - Opened by raucao over 6 years ago
#166 - build version 11
Pull Request -
State: closed - Opened by michielbdejong over 6 years ago
#165 - Add Last-Modified date to folder listings
Pull Request -
State: closed - Opened by raucao over 6 years ago
#164 - Add Last-Modified date to folder listings
Pull Request -
State: closed - Opened by raucao over 6 years ago
- 1 comment
#163 - Content negotiation for folders
Issue -
State: closed - Opened by wiktor-k over 6 years ago
- 2 comments
#162 - Encoding slashes in pathnames allowed?
Issue -
State: open - Opened by raucao almost 7 years ago
- 2 comments
Labels: enhancement, question
#161 - Improve specs and examples for 412 responses
Pull Request -
State: closed - Opened by raucao almost 7 years ago
- 1 comment
#160 - Remove duplicate paragraph
Pull Request -
State: closed - Opened by raucao almost 7 years ago
- 1 comment
#159 - Add 413 as example response code
Pull Request -
State: closed - Opened by raucao almost 7 years ago
- 7 comments
#158 - Require Last-Modified dates
Issue -
State: closed - Opened by raucao almost 7 years ago
- 20 comments
Labels: enhancement
#157 - V10
Pull Request -
State: closed - Opened by michielbdejong about 7 years ago
#156 - duplicate content, paragraphs line 320 and line 329
Issue -
State: open - Opened by michielbdejong over 7 years ago
Labels: bug
#155 - Version 09
Pull Request -
State: closed - Opened by michielbdejong over 7 years ago
- 5 comments
#154 - Support for passwordless login (FIDO UAF, TREZOR Connect)
Issue -
State: open - Opened by slush0 almost 8 years ago
- 4 comments
#153 - Release 08
Pull Request -
State: closed - Opened by michielbdejong about 8 years ago
#152 - No restrictions on content-type
Pull Request -
State: closed - Opened by untitaker about 8 years ago
- 2 comments
#151 - Simplify behavior on invalid content-type
Pull Request -
State: closed - Opened by untitaker about 8 years ago
- 9 comments
#150 - Bump spec version to -08
Pull Request -
State: closed - Opened by michielbdejong about 8 years ago
- 4 comments
#149 - Client: Drop OAuth parameters on server-first flow
Pull Request -
State: closed - Opened by untitaker over 8 years ago
- 5 comments
#148 - Server-first auth flow: Client behavior on invalid input ill-defined
Issue -
State: closed - Opened by untitaker over 8 years ago
- 4 comments
Labels: enhancement
#147 - Accept-Ranges header required, but where?
Issue -
State: open - Opened by untitaker over 8 years ago
Labels: bug, clarity
#146 - MAY ignore -> MUST ignore client_id, fix #143
Pull Request -
State: closed - Opened by michielbdejong over 8 years ago
- 8 comments
#145 - Simplify server-first auth
Pull Request -
State: closed - Opened by untitaker over 8 years ago
#144 - Storage-first auth flow should not shortcut normal OAuth flow.
Issue -
State: closed - Opened by untitaker almost 9 years ago
- 21 comments
Labels: enhancement, security
#143 - Value of client_id MUST be equal to origin of the redirect_uri?
Issue -
State: closed - Opened by michielbdejong about 9 years ago
- 2 comments
Labels: security
#142 - Remove false changelog entry
Pull Request -
State: closed - Opened by untitaker about 9 years ago
- 3 comments
#141 - client_id is already mandated by OAuth
Pull Request -
State: closed - Opened by untitaker about 9 years ago
- 9 comments
#140 - Cache-Control: no-cache also on failures?
Issue -
State: closed - Opened by ghost about 9 years ago
- 15 comments
Labels: clarity
#139 - Think of a way to implement server-to-client push notification
Issue -
State: open - Opened by michielbdejong about 9 years ago
- 16 comments
#138 - rationale for ETag update propagation on change
Issue -
State: closed - Opened by ghost about 9 years ago
- 10 comments
Labels: question
#137 - Consider need for MOVE verb
Issue -
State: open - Opened by michielbdejong about 9 years ago
- 7 comments
#136 - Mention comparison with WebDAV in the introduction
Issue -
State: open - Opened by michielbdejong about 9 years ago
- 4 comments
#135 - Whether to mention conditional or unconditional requests in the intro
Issue -
State: open - Opened by michielbdejong about 9 years ago
- 1 comment
#134 - Whether or not to mention response bodies for error responses
Issue -
State: open - Opened by michielbdejong about 9 years ago
- 2 comments
#133 - Point about updating version of folders left empty
Issue -
State: closed - Opened by michielbdejong about 9 years ago
- 2 comments
#132 - Change all ACAO values to *
Issue -
State: open - Opened by michielbdejong about 9 years ago
- 1 comment
#131 - Find a proper way of supporting resumable uploads
Issue -
State: open - Opened by michielbdejong about 9 years ago
- 5 comments
#130 - Redefinition of HTTP: Content-Type on PUT
Issue -
State: closed - Opened by untitaker about 9 years ago
- 11 comments
#129 - Changes in draft-dejong-remotestorage-06 but not in source.txt
Issue -
State: closed - Opened by untitaker about 9 years ago
- 4 comments
#128 - Use IRIs instead of URIs
Issue -
State: open - Opened by untitaker about 9 years ago
#127 - Frko 06 review 2 - rest
Pull Request -
State: closed - Opened by michielbdejong about 9 years ago
- 2 comments
#126 - Upgrade notes
Issue -
State: open - Opened by raucao about 9 years ago
- 2 comments
#125 - restructure specification
Issue -
State: open - Opened by ghost about 9 years ago
- 1 comment
#124 - Optionally support byte ranges support on PUT requests.
Issue -
State: open - Opened by michielbdejong about 9 years ago
- 19 comments
#123 - Clarify terminology around empty vs non-empty
Pull Request -
State: closed - Opened by untitaker about 9 years ago
- 2 comments
#122 - Remove syntax specification of etags
Pull Request -
State: closed - Opened by untitaker about 9 years ago
- 7 comments
#121 - Restrict set of filenames allowed
Issue -
State: closed - Opened by untitaker about 9 years ago
- 1 comment
#120 - client_id is already mandated by OAuth
Pull Request -
State: closed - Opened by untitaker about 9 years ago
- 1 comment
#119 - Incorrect usage of URI_ENCODE
Issue -
State: open - Opened by untitaker about 9 years ago
- 1 comment
Labels: bug, clarity
#118 - remove PUT range request mention, issue #117
Pull Request -
State: closed - Opened by ghost about 9 years ago
- 6 comments
#117 - remove PUT range request support or define it
Issue -
State: closed - Opened by ghost about 9 years ago
- 12 comments
Labels: bug, clarity
#116 - Frko 06 review 2
Pull Request -
State: closed - Opened by ghost about 9 years ago
- 6 comments
#115 - review of 06 spec
Pull Request -
State: closed - Opened by ghost about 9 years ago
- 1 comment
#114 - Restrict set of filenames allowed
Pull Request -
State: closed - Opened by michielbdejong about 9 years ago
#113 - Restrict set of filenames allowed
Pull Request -
State: closed - Opened by untitaker about 9 years ago
- 12 comments
#112 - Add recommendation to avoid unsafe/reserved chars
Pull Request -
State: closed - Opened by untitaker about 9 years ago
- 3 comments
#111 - SPDY -> HTTP/2, fix #102
Pull Request -
State: closed - Opened by michielbdejong about 9 years ago
- 6 comments
#110 - Identify app by origin of redirect_uri
Pull Request -
State: closed - Opened by michielbdejong about 9 years ago
- 14 comments
#109 - Allow leaving out CORS headers on 304s
Pull Request -
State: closed - Opened by michielbdejong about 9 years ago
- 3 comments
#108 - Remove outdated requirement of echoing back origin in CORS
Pull Request -
State: closed - Opened by michielbdejong about 9 years ago
- 1 comment
#107 - Allow leaving out 'me@' in user address
Pull Request -
State: closed - Opened by michielbdejong about 9 years ago
- 34 comments
#106 - add 413 (payload too large) to list of supported response codes
Issue -
State: closed - Opened by ghost about 9 years ago
- 15 comments
#105 - Clarify 401 vs. 403
Pull Request -
State: closed - Opened by michielbdejong about 9 years ago
- 6 comments
#104 - Clarify whether apps are expected to have their own subdomain
Issue -
State: closed - Opened by untitaker about 9 years ago
- 9 comments
#103 - define URI_ENCODE
Issue -
State: open - Opened by ghost over 9 years ago
- 71 comments
#102 - no longer mention speedy, but http 2.0
Issue -
State: closed - Opened by ghost over 9 years ago
#101 - use client_id to identify clients
Issue -
State: closed - Opened by ghost over 9 years ago
- 19 comments
#100 - CORS on 304?
Issue -
State: open - Opened by ghost over 9 years ago
- 14 comments
#99 - Update webfinger example to conform to its spec
Pull Request -
State: closed - Opened by untitaker over 9 years ago
- 1 comment
#98 - Clarify that folders are not created for each GET
Pull Request -
State: closed - Opened by untitaker over 9 years ago
- 7 comments
#97 - Allow HEAD requests in public category
Pull Request -
State: closed - Opened by untitaker over 9 years ago
- 1 comment
#96 - Narrow scope of 401 responses
Pull Request -
State: closed - Opened by untitaker over 9 years ago
#95 - Add clear rationale for requiring Expires: 0
Issue -
State: closed - Opened by untitaker over 9 years ago
- 17 comments
#94 - GET requests are allowed for /public/. Why not HEAD?
Issue -
State: closed - Opened by untitaker over 9 years ago
- 1 comment
#93 - What etag to choose for empty folder listings?
Issue -
State: closed - Opened by untitaker over 9 years ago
- 14 comments
#92 - Rationale for disallowing wildcards in CORS GET headers
Issue -
State: closed - Opened by untitaker over 9 years ago
- 6 comments