Sap v0.1.0 Sap.Combinators.Success View Source

Success responses

Link to this section Summary

Functions

The request has been received but not yet acted upon. It is non-committal, meaning that there is no way in HTTP to later send an asynchronous response indicating the outcome of processing the request. It is intended for cases where another process or server handles the request, or for batch processing

The request has succeeded and a new resource has been created as a result of it. This is typically the response sent after a PUT request

There is no content to send for this request, but the headers may be useful. The user-agent may update its cached headers for this resource with the new ones

The request has succeeded. The meaning of a success varies depending on the HTTP method

Link to this section Functions

The request has been received but not yet acted upon. It is non-committal, meaning that there is no way in HTTP to later send an asynchronous response indicating the outcome of processing the request. It is intended for cases where another process or server handles the request, or for batch processing.

The request has succeeded and a new resource has been created as a result of it. This is typically the response sent after a PUT request.

There is no content to send for this request, but the headers may be useful. The user-agent may update its cached headers for this resource with the new ones.

The request has succeeded. The meaning of a success varies depending on the HTTP method:

  • GET: The resource has been fetched and is transmitted in the message body.
  • HEAD: The entity headers are in the message body.
  • POST: The resource describing the result of the action is transmitted in the message body.
  • TRACE: The message body contains the request message as received by the server