Skip to content

Commit

Permalink
do not mention response bodies for errors, no point to have those for…
Browse files Browse the repository at this point in the history 
… the storage API
  • Loading branch information
François Kooman committed Nov 25, 2015
1 parent 7e29755 commit 9f8a4e2
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions draft-dejong-remotestorage-06.txt
View file
Original file line number Diff line number Diff line change
Expand Up @@ -286,8 +286,8 @@ Internet-Draft remoteStorage November 2015
If not exactly one Content-Type header was received as part of a
PUT request, the Content-Type header value contains non-ASCII
characters, or it is unreasonably long, the server MAY refuse to
process the request, and instead respond with a descriptive error
message in the body, and a http response code from the 4xx range.
process the request, and instead respond with a HTTP response code
from the 4xx range.

The response MUST contain a strong ETag header, with the document's
new version (for instance a hash of its contents) as its value.
Expand Down

3 comments on commit 9f8a4e2

@michielbdejong
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They're useful for debugging!

r-

@michielbdejong
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just mentioning a nice practice as a MAY doesn't do any harm, does it? I guess this is a general discussion.

We can split the spec into:

Main part

  • refer to HTTP, TLS, CORS, OAUTH, BEARER, WEBFINGER.
  • restrict HTTP verbs to GET, PUT, DELETE
  • define the folder description format
  • define that everything except the special 'public' folder is private
  • define the OAuth scope names

Implementation suggestions

  • everything else :)

@michielbdejong
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Discussion about this proposal can be continued in #134.

Please sign in to comment.