13.4.3 Response

13.4.3 Response (Current)
Prev	13.4 Request Transaction	Next

The response shall have the following syntax:

version SP status-code SP reason-phrase CRLF

[retry-after CRLF]

CRLF

[payload]

Table 13.4.3-1 shows some common status codes corresponding to this transaction. See also Section 8.5 for additional status codes.

Table 13.4.3-1. Status Code Meaning

Status	Code	Meaning
Success	200 (OK)	The origin server finished processing the storage commitment request; the payload describes in detail what referenced SOP Instances have been committed for safekeeping, and what Instances have not.
Success	202 (Accepted)	The origin server has not finished processing the storage commitment request yet; there is no payload. The user agent is expected to follow-up with the Result Check transaction, as described in Section 13.5, to retrieve the result of the storage commitment request.
Failure	400 (Bad Request)	The origin server cannot handle the storage commitment request because of errors in the request headers or parameters.
	409 (Conflict)	The origin server cannot handle the storage commitment request because the provided transaction UID is already in use.
	503 (Service Unavailable)	The origin server cannot handle the storage commitment request; this may be a temporal or permanent state.

Prev	Up	Next
13.4.2 Behavior	Home	13.4.3.2 Response Header Fields