13.5.3 Response

13.5.3 Response (Current)
Prev	13.5 Result Check Transaction	Next

The response shall have the following syntax:

version SP status-code SP reason-phrase CRLF

[retry after CRLF]

CRLF

[payload]

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

Table 13.5.3-1. Status Code Meaning

Status	Code	Meaning
Success	200 (OK)	The origin server finished processing the Request transaction identified by the supplied Transaction UID (see Section 13.4); the payload contains the result.
Success	202 (Accepted)	The origin server has not yet finished processing the Request transaction identified by the supplied Transaction UID; there is no payload. The user agent is expected to follow-up again with the Result Check transaction, to retrieve the result of the storage commitment request.
Failure	404 (Not Found)	The origin server cannot find the storage commitment request result identified by the supplied Transaction UID.
	410 (Gone)	The origin server can no longer provide the storage commitment request result identified by the supplied Transaction UID.
	503 (Service Unavailable)	The origin server cannot handle the Result Check request; this may be a temporary or permanent state.

The 404 (Not Found) status code may be caused by an incorrect Transaction UID that has been supplied by the user agent, or the origin server may have deleted the applicable result.
The 410 (Gone) status code may be caused by the origin server deleting the applicable result, but still having a record of the Transaction UID.
When the 404 (Not Found) or the 410 (Gone) status code is returned, the user agent might initiate a new storage commitment request. When the 503 (Service Unavailable) status code is returned, the user agent might retry later with another Result Check transaction.

Prev	Up	Next
13.5.2 Behavior	Home	13.5.3.2 Response Payload