DICOM PS3.18 2020c - Web Services

10.5.3.2 Response Header Fields (Current)
Prev | 10.5.3 Response | Next

#### 10.5.3.2 Response Header Fields

The origin server shall support header fields as required in Table 10.5.3-2.

Table 10.5.3-2. Response Header Fields

Name | center | Origin Server Usage | Description
--- | --- | --- | ---
Content-Type | media-type | M | The media type of the response payload, if present.
Content-Encoding | encoding | C | Shall be present if the response payload has a content encoding. See Section 8.4.3.
Content-Length | uint | C | Shall be present if the response payload does not have a content encoding. See Section 8.4.3.
Content-Location | url | C | Shall be present if a new resource was created. The value is the URL of the representation contained in the request payload. May be present otherwise
Location | url | C | Shall be present if a new resource was created. The value is the URL of the created resource. May be present otherwise

All success responses shall also contain the Content Representation (see Section 8.4.2) and Payload header fields (see Section 8.4.3) with appropriate values.

It is recommended that the text returned in the Warning header field (see [RFC7234] Section 5.5) contain a DICOM Status Code (see PS3.4 and Annex C “Status Type Encoding (Normative)” in PS3.7) and descriptive reason. For example:

    Warning: A700 <service>: Out of memory

See also Section 8.4.

Prev | Up | Next
10.5.3 Response | Home | 10.5.3.3 Response Payload

DICOM PS3.18 2020c - Web Services