N.7.3.3.6 Storage Commitment Service
N.7.3.3.6.1 Request Transaction As Origin Server
Table N.7.3.3.6.1-1 lists the Status Codes that an origin server supports for the Request Transaction of the Storage Commitment Service and the condition in which any of the listed Status Codes is sent.
[Describe below the condition in which the application sends the specific Status Codes in the Request Transaction response as origin server.]
Table N.7.3.3.6.1-1. Status Codes of Origin Server for Request Transaction
|
Status
|
Code
|
Condition
|
|
Success
|
200 (OK)
|
The origin server finished processing the storage commitment request
|
|
202 (Accepted)
|
The origin server has not finished processing the storage commitment request yet
|
|
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
|
N.7.3.3.6.2 Request Transaction As User Agent
Table N.7.3.3.6.2-1 lists the Status Codes that a user agent supports for the Request Transaction of the Storage Commitment Service and defines the application behavior, when encountering any of the listed Status Codes.
[Describe below the behavior of the application when it receives various Status Codes in the Request Transaction response.]
Table N.7.3.3.6.2-1. Status Codes of User Agent for Request Transaction
|
Status
|
Code
|
Behavior
|
|
Success
|
200 (OK)
|
Mark all SOP Instances for which the origin server committed safe storage as ready for deletion
|
|
202 (Accepted)
|
Retry later to get the result of the request
|
|
Failure
|
400 (Bad Request)
|
Reformat the request to proper HTTP
|
|
409 (Conflict)
|
Retry with another transaction UID
|
|
*
|
Any other code
|
Do further analysis
|
N.7.3.3.6.3 Result Check Transaction As Origin Server
Table N.7.3.3.6.3-1 lists the Status Codes that an origin server supports for the Result Check Transaction of the Storage Commitment Service and the condition in which any of the listed Status Codes is sent.
[Describe below the condition in which the application sends the specific Status Codes in the Result Check Transaction response as origin server.]
Table N.7.3.3.6.3-1. Status Codes of Origin Server for Result Check Transaction
|
Status
|
Code
|
Condition
|
|
Success
|
200 (OK)
|
The origin server finished processing the storage commitment request
|
|
202 (Accepted)
|
The origin server has not finished processing the storage commitment request yet
|
|
Failure
|
404 (Not Found)
|
The origin server cannot find the storage commitment request result
|
|
410 (Gone)
|
The origin server can no longer provide the storage commitment request result
|
|
503 (Service Unavailable)
|
The origin server cannot handle the result check request; this may be a temporary or permanent state
|
N.7.3.3.6.4 Result Check Transaction As User Agent
Table N.7.3.3.6.4-1 lists the Status Codes that a user agent supports for the Result Check Transaction of the Storage Commitment Service and defines the application behavior when encountering any of the listed Status Codes.
[Describe below the behavior of the application when it receives various Status Codes in the Result Check Transaction response.]
Table N.7.3.3.6.4-1. Status Codes of User Agent for Result Check Transaction
|
Status
|
Code
|
Behavior
|
|
Success
|
200 (OK)
|
Mark all SOP Instances for which the origin server committed safe storage as ready for deletion
|
|
202 (Accepted)
|
Retry later to get the result of the request
|
|
Failure
|
404 (Not Found)
|
Start all over with a storage commitment request
|
|
410 (Gone)
|
Start all over with a storage commitment request
|
|
*
|
Any other code
|
Do further analysis
|