The response has the following syntax:
version SP status-code SP reason-phrase CRLF
Content-Type: dicom-media-type CRLF
[ETag: entity-tag CRLF]
[Last-Modified: HTTP-date CRLF]
*(header-field CRLF)
CRLF
Payload
6.10.3.2.3.1 Status Codes
The response shall have an appropriate status code. Table 6.10.3.2.3.1-1 contains the most common status codes for this transaction.
Table 6.10.3.2.3.1-1. Status Codes
|
Code
|
Description
|
|
200 (OK)
|
Indicates that the instance was successfully retrieved.
|
|
304 (Not Modified)
|
Indicates that the user agent's current representation is up to date, so no payload was returned. This status code shall only be returned for a Conditional Retrieve request containing an If-None-Match header field.
|
|
400 (Bad Request)
|
Indicates that the origin server did not store any of the representations contained in the request payload because of errors in the request message. For example, an invalid Query Parameter or an invalid SOP instance.
|
|
404 (Not Found)
|
Indicates that 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 SOP Instance not on server.
|
|
406 (Unsupported
Media Type)
|
Indicates that the origin server does not support any of the Acceptable Media Types.
|
See [RFC7231]
Section 6.
6.10.3.2.3.2 Response Header Fields
Table 6.10.3.2.3.2-1. Request Header Fields
|
Header Field
|
Value
|
Usage
|
Requirements
|
|
Content-Type
|
dicom-media-type
|
M
|
|
|
Content-Length
|
uint
|
C
|
Shall be present if no transfer coding has been applied. Shall be absent otherwise.
|
|
Transfer-Encoding
|
encoding
|
C
|
Shall be present if a transfer coding has been applied. Shall be absent otherwise.
|
|
ETag
|
entity-tag
|
C
|
Shall be present if the response status code is 200 or 204.
|
6.10.3.2.3.3 Response Payload
A success response shall have a payload containing the DICOM instance specified by the target resource.
A failure response shall have a payload describing the error.