6.3 HTTP Response

The response shall be an HTTP Response Message as specified in IETF RFC2616.

Note: The content of the message-body varies according to the Media type as defined below.

6.3.1 Body of single DICOM MIME sub-type part response

6.3.1.1 MIME Type

The MIME type shall be ‘application/dicom‘, as specified in IETF RFC3240.

6.3.1.2 Content

The body content shall be a "Part 10 File" that includes a meta-header as defined in PS 3.10.

6.3.1.3 Transfer syntax

The returned DICOM object shall be encoded using one of the transfer syntaxes specified in the transfer syntax query parameter as defined in Section 8.2.11 below. By default, the transfer syntax shall be "Explicit VR Little Endian".

Note: This implies that retrieved images are sent un-compressed by default.

6.3.2 Body of Non–DICOM MIME type response

6.3.2.1 MIME Type

The MIME type shall be one on the MIME types defined in the contentType parameter, preferably the most desired by the Web Client, and shall be in any case compatible with the ‘Accept’ field of the GET method.

Note: The HTTP behavior is that an error (406 – Not Acceptable) is returned if the required content type cannot be served.

6.3.2.2 Content

The content shall be a single MIME part containing the object to be retrieved.

Note: Multiple objects in a response are not supported by this standard. The parameters select only a single object to retrieve. Most current Web Clients are able to retrieve single objects, within a "non multipart" MIME body, and are not able to support multipart/related or multipart/mixed responses.