CP-1698 Remove ETag requirement in Non-Patient Instance Restful service <informaltable rules="all" frame="box"> <tr> <td rowspan="1" colspan="1" valign="top"><para>Status</para></td> <td rowspan="1" colspan="1" valign="top"><para>Assigned</para></td> </tr> <tr> <td rowspan="1" colspan="1" valign="top"><para>Date of Last Update</para></td> <td rowspan="1" colspan="1" valign="top"><para>2017/03/26</para></td> </tr> <tr> <td rowspan="1" colspan="1" valign="top"><para>Person Assigned</para></td> <td rowspan="1" colspan="1" valign="top"><para>David Clunie</para><para><link xl:href="mailto:dclunie@dclunie.com"/></para></td> </tr> <tr> <td rowspan="1" colspan="1" valign="top"><para>Submitter Name</para></td> <td rowspan="1" colspan="1" valign="top"><para>David Clunie</para><para><link xl:href="mailto:dclunie@dclunie.com"/></para></td> </tr> <tr> <td rowspan="1" colspan="1" valign="top"><para>Submission Date</para></td> <td rowspan="1" colspan="1" valign="top"><para>2017/02/22</para></td> </tr> </informaltable> <informaltable rules="all" frame="box"> <tr> <td rowspan="1" colspan="1" valign="top"><para>Correction Number CP-1698</para></td> </tr> <tr> <td rowspan="1" colspan="1" valign="top"><para>Log Summary: Remove ETag requirement in Non-Patient Instance Restful service</para></td> </tr> <tr> <td rowspan="1" colspan="1" valign="top"> <para>Name of Standard</para> <para>PS3.18</para> </td> </tr> <tr> <td rowspan="1" colspan="1" valign="top"><para>Rationale for Correction:</para> <para>Sup 194 introduced a requirement to send an ETag with a successful response.</para> <para>This is inappropriate since ETags may be used to imply versioning, which needs to be handled at a DICOM payload level or at the very least consistently across all services (RESTful or not). In addition, they may pose a privacy risk and be abused (like Cookies). Further, they may be removed or modified by proxies and caches over which the origin-server has no control.</para> <para>Remove the requirement.</para> <para>If ETags are ever going to be used in the standard, extensive discussion of the details is required.</para> <para>This does not prevent the optional use of ETags if they are deemed appropriate for a specific deployment.</para> </td> </tr> <tr> <td rowspan="1" colspan="1" valign="top">Correction Wording:</td> </tr> </informaltable> </chapter> <chapter> <title/> <informaltable rules="all" frame="box"> <tr> <td> <para><emphasis role="italic">Amend DICOM PS3.18 as follows (changes to existing text are bold and <emphasis role="bold"><emphasis role="underline">underlined</emphasis></emphasis> for additions and <emphasis role="bold"><emphasis role="strikethrough">struckthrough</emphasis></emphasis> for removals):</emphasis></para> </td> </tr> </informaltable> <section xml:id="sect_6.10.3.1" label="6.10.3.1" status="4"> <title>Retrieve Capabilities Transaction
Response
Response Header Fields
Response Header Fields
Header Field Value Usage Requirements
Content-Type media-type M
Content-Length uint C Shall be present if no transfer coding has been applied. Shall be absent otherwise.
Transfer-Encoding encoding C Shall be present if a transfer coding has been applied. Shall be absent otherwise.
ETag entity-tag C Shall be present if the response status code is 200.
Retrieve Transaction
Response
Response Header Fields
Request Header Fields
Header Field Value Usage Requirements
Content-Type dicom-media-type M
Content-Length uint C Shall be present if no transfer coding has been applied. Shall be absent otherwise.
Transfer-Encoding encoding C Shall be present if a transfer coding has been applied. Shall be absent otherwise.
ETag entity-tag C Shall be present if the response status code is 200 or 204.