The response shall have the following syntax:
version SP status-code SP reason-phrase CRLF
[Content-Type: media-type CRLF]
[(Content-Length: uint / Transfer-Encoding: encoding) CRLF]
[Content-Location: url CRLF]
*(header-field CRLF)
CRLF
[Status Report]
Table 12.5.3-1 shows some common status codes corresponding to this transaction. See also Section 8.5 for additional status codes.
Table 12.5.3-1. Status Code Meaning
|
Status
|
Code
|
Meaning
|
|
Success
|
200 (OK)
|
The origin server successfully stored or created at least one of the representations contained in the request payload and is returning a response payload.
|
|
202 (Accepted)
|
The origin server successfully validated the request message but has not yet stored or created the representations in the request payload. The origin server may or may not have validated the payload.
The user agent can use a Query or Retrieve transaction later to determine if the request has completed.
|
|
Failure
|
400 (Bad Request)
|
The was a problem with the request. For example:
-
the origin server did not store any of the representations contained in the request payload because of errors in the request message,
-
the request contained an invalid Query Parameter,
-
the request referenced an invalid Instance.
|
|
404 (Not Found)
|
The origin server did not find a current representation for the Target Resource or is not willing to disclose that one exists. For example, an unsupported IOD, or Instance not on server.
|
|
409 (Conflict)
|
The request could not be completed due to a conflict with the current state of the Target Resource.
|
|
415 (Unsupported Media Type)
|
The origin server does not support the media type specified in the Content-Type header field of the request, and none of the representations contained in the request were processed or stored.
|