2.7. Status Codes
The OpenShift REST API attempts to return standard HTTP status codes. The more common status codes are shown in the following table along with a brief description of each.
| Code | Text | Description |
|---|---|---|
| 200 | OK | Standard response for successful HTTP requests. |
| 201 | Created | The resource was successfully created. |
| 204 | No content | The requested delete operation was successful. |
| 301 | Moved Permanently | The resource has moved, and all future requests should be made to the new URI. |
| 400 | Bad Request | Invalid request due to bad syntax. |
| 401 | Unauthorized | Authentication has failed, or was not provided. |
| 403 | Forbidden | The request is understood, but server is refusing to respond. |
| 404 | Not Found | The requested resource cannot be found. |
| 406 | Not Acceptable | The content from the requested resource is not acceptable according to the Accept headers. Possibly due to version requested, or it no longer being supported. |
| 409 | Conflict | The request could not be processed because of conflict in the request. |
| 410 | Gone | The resource is no longer available, and will not be available again. |
| 422 | Unprocessable Entity | The request was well formed, but was not followed due to semantic errors. |
| 500 | Internal Server Error | A generic error message when something is broken. |
| 502 | Bad Gateway | Server was acting as a gateway or proxy, and received an invalid response. |
| 503 | Service Unavailable | The server is currently unavailable; possibly down for maintenance. |
| 504 | Gateway Timeout | The server was acting as a gateway or proxy and did not receive a timely response. |
