6.2 WADO-URI Request
Prev | 6 Data Communication Requirements | Next

## 6.2 WADO-URI Request

The HTTP Request used shall use the GET method as defined in IETF RFC7230.

### 6.2.1 Parameters of the HTTP Request

The parameters of the <query> component of the Request-URI to be sent to the web Server through the HTTP GET method request shall be represented as defined in IETF RFC3986.

### Note

1. Other components of the Request-URI depend on the configuration, e.g., location and script language of the Web Enabled DICOM Server.

2. The means by which the Web Client System obtains the value of the necessary parameters for web accessing of DICOM objects is out of the scope of the standard.

### 6.2.2 List of Media Types Supported in the Response

The "Accept" field of the GET method request shall specify the Media type(s) acceptable to the Web Client System. The(se) Media type(s) shall include at least the items of the list of MIME types specified in Section 7 of this standard devoted to the DICOM persistent object types.

### Note

Typically the Accept field will be sent by a Web Client as "*/*". An optional parameter specifies the MIME type(s) preferred by the Web Client, as a subset of those specified in the "Accept" field.

### 6.2.3 List of Character Sets Supported in the Response

The "Accept-charset" field of the GET method request shall specify the character set of the object to be retrieved. If the "Accept-charset" field of the GET method is not present, or the Web Enabled DICOM Server does not support the specified character set, the character set of the response will be at the discretion of the Web Enabled DICOM Server.

Note Typically the user of a Web Client does not have control over the "Accept-charset" field. An optional parameter specifies the character set to be used in the returned object.

Prev | Up | Next
6 Data Communication Requirements | Home | 6.3 WADO-URI Response