search

remotestorage / spec

remoteStorage Protocol Specification
https://tools.ietf.org/html/draft-dejong-remotestorage
87 stars 5 forks source link

HTTP return codes #34

Closed ghost closed 8 years ago

ghost commented 11 years ago 

             path or unrecognized http verb, etcetera), as well as for
             all PUT and DELETE requests to folders,'''

For unrecognized verbs I think a 405 should be returned ("method not allowed")

```    \* 401 for all requests that don't have a bearer token with
             sufficient permissions,'''

This is "out of scope" here, it can be listed but is actually part of the Bearer token spec. That one states that for missing tokens or invalid tokens a 401 should be returned, and a 403 when there is not sufficient permission.
michielbdejong commented 10 years ago

this is fixed since we now refer to [HTTP] and [BEARER] for the instructions about what status codes to return when, and the checklist is still in the text but is now non-normative

ghost commented 8 years ago

Yeah, but I'd like to see it added to the checklist, just to avoid any confusion. For example, a 403 would be returned when writing/reading to another user's folder, a folder where you didn't not get scope for.

michielbdejong commented 8 years ago

Can you propose your change in a PR?

ghost commented 8 years ago

See https://github.com/remotestorage/spec/pull/91

untitaker commented 8 years ago

I think this can be closed.