Actions
Bug #3483
closed[Keep] Keep uses appropriate HTTP status codes for failed DELETE requests
Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
Keep
Target version:
-
Story points:
1.0
Description
When a DELETE request fails because a call to the API server could not be executed successfully, the HTTP status returned by the API server should be passed through to Keep's DELETE response:
- Respond 403 Forbidden if the token is valid (users.get responds 200) but does not pass is_admin/scopes verification, or users.get responds 403 (which is another scope problem).
- Respond 401 Unauthorized If the token is invalid (users.get responds 401) (This probably means the token has expired.)
- define an ArvadosApiError type that includes the API server HTTP status code
- change sdk.ArvadosClient.CallRaw to return an HTTP status instead of an error message
Updated by Ward Vandewege about 10 years ago
- Subject changed from Keep uses appropriate HTTP status codes for failed DELETE requests to [Keep] Keep uses appropriate HTTP status codes for failed DELETE requests
Updated by Tom Clegg about 10 years ago
- Target version changed from 2014-08-27 Sprint to Arvados Future Sprints
Updated by Tom Clegg over 9 years ago
215372746216e1c348231b6585a6e0fb9c505af4 makes the HTTP status code (and error messages!) available to the caller after an API error.
Updated by Tom Clegg over 7 years ago
- Target version deleted (
Arvados Future Sprints)
Actions