...
| Exception | HTTP Code | Description / Idea behind | ||||||
|---|---|---|---|---|---|---|---|---|
| ZfExtended_BadMethodCallException | 405 Method Not Allowed | Means that the used HTTP Method is not allowed / not implemented. So a usage makes only sense on the controller level. | ||||||
| ZfExtended_NotAuthenticatedException | 401 Unauthorized | Means the the user is not authorized, so in the request there was no information to identify the user. This error should redirect the user in the GUI to the login page. | ||||||
| ZfExtended_NotFoundException | 404 Not Found | Is used in application routing, is thrown when the whole requested route is not found (invalid URL). | ||||||
| ZfExtended_Models_Entity_NotFoundException | 404 Not Found | Is used if an entity can not be found (if it is loaded via an id or guid) | ||||||
| ZfExtended_NoAccessException ZfExtended_Models_Entity_NoAccessException | 403 Forbidden | The user (authenticated or not) is not allowed to see / manipulate the requested resource. TODO: clear the difference between both exceptions. | ||||||
| TODO new Unprocesseable Entity Exception (or reuse ValidateException?) | 422 Unprocessable Entity | Should be used PUT/POSTed content does prevent normal processing: Wrong parameters, missing parameters. | ||||||
| ZfExtended_Models_Entity_Conflict | 409 Conflict | Should be used if the status of the entity does prevent normal processing: The entity is locked, the entity is used/referenced in other places. In other words: the entity it self is reasonable that the request can not be processed. | ||||||
ZfExtended_VersionConflictException | 409 Conflict | Must only be used if entity can not be saved due a changed entity version. The classical usage of the 409 HTTP error: the entity was changed in the meantime. | ||||||
| ZfExtended_BadGateway TODO implement 504 Gateway Timeout | 502 Bad Gateway | Should be used if our request calls internally a third party service, and the third party service or the communication with it does not work. | ||||||
| ZfExtended_Models_Entity_NotAcceptableException TODO 422 Unprocessable Entity | 406 Not Acceptable | TODO: 406 Not Acceptable → makes no sense in the currently used application context, only in the REST router if invalid content according to the accept header is given. Should be converted to: 422 Unprocessable Entity | ValidateException | 422 Unprocessable Entity | Use this exception if the given data in the request can not be validated or contains non processable data. | ZfExtended_ValidateException | 400 Bad Request | TODO Since a Bad Request should only be given if the syntax is invalid (invalid JSON), the ValidateException should remain but should return a 422 instead? |
| ZfExtended_FileUploadException | 400 Bad Request | TODO, currently not used. Should be used in the context of errors with uploaded data | ||||||
| ZfExtended_Models_MaintenanceException | 503 Service Unavailable | Only usable in the context of the maintenance mode | ||||||
| ZfExtended_Models_Entity_Exceptions_IntegrityDuplicateKey | TODO → specific exception? No direct HTTP code | Is thrown on saving entities and the underlying DB call returns a "integrity constraint violation 1062 Duplicate entry" error: That means an entity with such key does already exist (entities with additional unique keys, customer number or user login). | ||||||
| ZfExtended_Models_Entity_Exceptions_IntegrityConstraint | TODO → specific exception? No direct HTTP code | Is thrown on saving/deleting entities and the underlying DB call returns one of the following "integrity constraint violation" error:
| ||||||
...