Berlioz status
Status that can be returned from generators and services and corresponding the HTTP parameters.
Generators must all returns a status. Berlioz computes the status for the service based on the status of each generator.
This can be controlled using the <response-code> element in the services.xml. The default rule is to use the highest values of all the statuses returned by the generators in a service.
Successful
| Name | HTTP Code | Description |
|---|---|---|
ok | 200 | The request has succeeded. |
created | 201 | The request has been fulfilled and resulted in a new resource being created. |
accepted | 202 | The request has been accepted for processing, but the processing has not been completed. |
no_content | 204 | The server has fulfilled the request but does not need to return any content. Berlioz will not send any content with the request. |
reset_content | 205 | The server has fulfilled the request and the user agent SHOULD reset the document view which caused the request to be sent. Berlioz will not send any content with the request. |
Redirection
| Name | HTTP Code | Description |
|---|---|---|
moved_permanently | 301 | The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD use one of the returned URIs. |
found | 302 | The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. |
see_other | 303 | The response to the request can be found under a different URI and SHOULD be retrieved using a GET method on that resource. |
temporary_redirect | 307 | The requested resource resides temporarily under a different URI. |
Client errors
| Name | HTTP Code | Description |
|---|---|---|
bad_request | 400 | The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications. |
forbidden | 403 | The server understood the request, but is refusing to fulfill it. |
not_found | 404 | The server has not found anything matching the Request-URI. |
conflict | 409 | The request could not be completed due to a conflict with the current state of the resource. |
gone | 410 | The requested resource is no longer available at the server and no forwarding address is known. |
Note
Where is 401? At present, Berlioz isn't designed to implement the security layer. It can however indicate when access to a resource is forbidden using 403.Server errors
| Name | HTTP Code | Description |
|---|---|---|
internal_server_error | 500 | The server encountered an unexpected condition which prevented it from fulfilling the request. |
not_implemented | 501 | The server does not support the functionality required to fulfill the request. |
bad_gateway | 502 | The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request. |
service_unavailable | 503 | The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. |
gateway_timeout | 504 | The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the URI or some other auxiliary server it needed to access in attempting to complete the request. |
Created on , last edited on