DICOM PS3.18 2019b - Web Services

11.6.3.2 Response Header Fields (Current)
Prev | 11.6.3 Response | Next

#### 11.6.3.2 Response Header Fields

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

Table 11.6.3-2. Response Header Fields

Name | center | Origin Server Usage | Description
--- | --- | --- | ---
Content-Type | media-type | M | The media-type of the payload
Content-Length | uint | C | Shall be present if no content encoding has been applied to the payload
Content-Encoding | encoding | C | Shall be present if a content encoding has been applied to the payload
Content-Location | url | O | Shall be present if the response has a payload containing a resource. See Section 8.4.3. May be present otherwise
Warning | see below | O | If the Target Workitem was modified by the origin server shall include one of the Warning header fields below.

If the Workitem was successfully updated but with modifications made by the origin server, the response shall include the following in the Warning header field:

    Warning: 299 <service>: The Workitem was updated with modifications.

If optional Attributes were rejected, the response shall include the following Warning header field:

    Warning: 299 <service>: Requested optional Attributes are not supported.

If the request was rejected with a failure status code, the response shall include a Warning header field with one of following messages that best describes the nature of the conflict:

    Warning: 299 <service>: The target URI did not reference a claimed Workitem.

    Warning: 299 <service>: The submitted request is inconsistent with the current state of the Workitem.

See also Section 8.4.

Prev | Up | Next
11.6.3 Response | Home | 11.6.3.3 Response Payload

DICOM PS3.18 2019b - Web Services