-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/13/2015 03:08 PM, Viliam Rockai wrote:
Another REST issue we should agree on: The standard for error
responses. I've found, that there are several standards we can
follow (or create our own):
My turn. Case:
Resource "resource1" belongs to user "user1".
User "user2" tries to access /resources/resource1 .
What should be the response? "Not found", because the resource
"resource1" doesn't exists on the context of "user2", or
Forbidden,
because the resource exists in our database, but "user2" can't access it?
- - Juca.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJU3gadAAoJECKM1e+fkPrXJS8H/3KgcizkKZekW+PZV4HpwlMo
+9MPDMxtxnPtXq0o5GYTdEL3uRHVqRwMK04Fwx5dYJ+2bJQ9EXFK/hQhg0mWuHzh
kSKGwBQD+zDb9IPHVUSKoYvkkXBcZjsQscYL6uNA/TiTp8pT+JxTw6aRkSylW/95
UOdC8aoEZQqGzOO2tBcwiIoF7TXa+tVuY5TgV/ldydBCbQgPl2/iQY++Mwj4h6ri
VEacrDoGe0sNrrEMOJf4YvyCXgkVWdeaviscZ816LQ2dKFU4CocgY/0IeGwlwz9F
IDevKUWqbrj+UXSjZoUh+p2+7dSJyjob2jfHev+TayC7nlbj6/TrSmTK0t7O7qg=
=r0UU
-----END PGP SIGNATURE-----