DICOM PS3.18 2020c - Web Services

8.3.3 Content Negotiation Query Parameters (Current)
Prev | 8.3 Query Parameters | Next

### 8.3.3 Content Negotiation Query Parameters

The parameters defined in this section are primarily designed for use in hyperlinks, i.e., URIs embedded in documents, where the Content Negotiation header fields (see Section 8.3.3) are not accessible.

#### 8.3.3.1 Accept Query Parameter

The Accept Query Parameter has the following syntax:

    accept      = accept-name "=" 1#(media-type [weight])
    accept-name = %s"accept"

The Accept Query Parameter has the same syntax as the Accept header field (see Section 8.4.3), except that it shall not have wildcards (<type>/* or */*). See Section 8.7.

### Note

1. The normal name of this parameter is "accept"; however, the URI Service uses an accept-name of "contentType". See Section 9.1.2.2.1.

2. The "%s" that prefixes the accept-name specifies that it is a case sensitive token. See [RFC7405].

The parameter value is a comma-separated list of one or more media-types.

The Accept Query Parameter should not be used when the user agent can specify the values by using the Accept header field.

All media types present in an Accept Query Parameter shall be compatible with a media range in the Accept header field, either explicitly or implicitly through wildcards.

### Note

For example, the presence of image/jpeg in the Accept Query Parameter will require the Accept header field to include one or more of the following values: image/jpeg, image/*, or */*.

If none of the Acceptable Media Types (see Section 8.7.5) are supported by the origin server, the origin server response shall be in the default media type for the Resource Category of the Target Resource. If there is no default media type defined for the Target Resource, the origin server response shall be 406 (Not Acceptable) and may include a payload containing an appropriate Status Report.

If a DICOM Media Type is present, non-DICOM Media Types shall not be present. If both DICOM and non-DICOM Media Types are present, the response shall be 400 (Bad Request), and may include a payload containing an appropriate Status Report.

Prev | Up | Next
8.3.2 Query Parameter Usage | Home | 8.3.3.2 Character Set Query Parameter

DICOM PS3.18 2020c - Web Services