DICOM PS3.18 2020c - Web Services

11.7.3.2 Response Header Fields (Current)
Prev | 11.7.3 Response | Next

#### 11.7.3.2 Response Header Fields

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

Table 11.7.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 | text | C | See below.

If the user agent specifies a Procedure Step State (0074,1000) Attribute with a value of "CANCELED" and the Workitem is already in that state, the response message shall include the following HTTP Warning header field:

    Warning: 299 <service>: The UPS is already in the requested state of CANCELED.

If the user agent specifies a Procedure Step State (0074,1000) Attribute with a value of "COMPLETED" and the UPS Instance is already in that state, the response message shall include the following HTTP Warning header field:

    Warning: 299 <service>: The UPS is already in the requested state of COMPLETED.

If the request was rejected with a failure status code, the response message shall include one of following messages in the HTTP Warning header field describing the nature of the conflict:

    Warning: 299 <service>: The Transaction UID is missing.

    Warning: 299 <service>: The Transaction UID is incorrect.

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

See also Section 8.4.

Prev | Up | Next
11.7.3 Response | Home | 11.7.3.3 Response Payload

DICOM PS3.18 2020c - Web Services