# DicomWeb Plugin

**URL:** https://discourse.orthanc-server.org/t/dicomweb-plugin/1218
**Category:** Google Groups archive
**Created:** [November 28, 2018, 7:16am UTC](https://discourse.orthanc-server.org/t/dicomweb-plugin/1218 "2018-11-28T07:16:03Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Felix\_Nensa](https://discourse.orthanc-server.org/letter_avatar_proxy/v4/letter/f/fbc32d/32.png) [@Felix\_Nensa](https://discourse.orthanc-server.org/u/Felix_Nensa)
#### Post date: [November 28, 2018, 7:16am UTC](https://discourse.orthanc-server.org/t/dicomweb-plugin/1218/1 "2018-11-28T07:16:03Z")

</div>

When inspecting the HTTP responses of the DicomWeb Plugin I found the plugin to respond with close delimited HTTP entities.  
Is there a specific reason why you do not send a “Content-Length” header or using chunked entities?  
Wouldn’t this enable more efficient use of resources like memory and re-using connections?

Felix

> GET /dicom-web/studies/1.2.3/series/1.3.3/instances/1.3.3 HTTP/1.1

> Host: localhost:8042

> Authorization: Basic ZmVTpnZhuuH5zYhWsaXlaW0xMjM=

> User-Agent: curl/7.52.1

> Accept: _/_

> 

\< HTTP/1.1 200 OK

\< Content-Type: multipart/related; type=application/dicom; boundary=5217EE14-94A0-4C25-AF11-14547AEC301E

- no chunk, no close, no size. Assume close to signal end

---

<div class="post-metadata">

### Author: ![jodogne](https://discourse.orthanc-server.org/user_avatar/discourse.orthanc-server.org/jodogne/32/1511_2.png) [@jodogne](https://discourse.orthanc-server.org/u/jodogne)
#### Post date: [November 29, 2018, 4:29pm UTC](https://discourse.orthanc-server.org/t/dicomweb-plugin/1218/2 "2018-11-29T16:29:13Z")

</div>

Hello,

The “Content-Length” HTTP header is not set in multipart answers, as the size of the individual parts is unknown in advance.

Sébastien-

---

<div class="post-metadata">

### Author: ![Felix\_Nensa](https://discourse.orthanc-server.org/letter_avatar_proxy/v4/letter/f/fbc32d/32.png) [@Felix\_Nensa](https://discourse.orthanc-server.org/u/Felix_Nensa)
#### Post date: [November 29, 2018, 6:40pm UTC](https://discourse.orthanc-server.org/t/dicomweb-plugin/1218/3 "2018-11-29T18:40:40Z")

</div>

Hi Sébastien, I see. Thanks for the explanation.

One more thing related to the header.  
Wouldn’t it per [https://tools.ietf.org/html/rfc2387#page-5](https://tools.ietf.org/html/rfc2387#page-5) be correct to put the type parameter in double quotes?

If I consume the response of the DicomWeb plugin with akka-http, it gives a respective error.  
I think it should be:

Content-Type: multipart/related; type= **“application/dicom”** ; boundary=5217EE14-94A0-4C25-AF11-14547AEC301E

Correct?

---

<div class="post-metadata">

### Author: ![jodogne](https://discourse.orthanc-server.org/user_avatar/discourse.orthanc-server.org/jodogne/32/1511_2.png) [@jodogne](https://discourse.orthanc-server.org/u/jodogne)
#### Post date: [November 29, 2018, 6:44pm UTC](https://discourse.orthanc-server.org/t/dicomweb-plugin/1218/4 "2018-11-29T18:44:39Z")

</div>

Hello,

Indeed, this has been fixed by the following changeset that is pending in the mainline, and that will be part of forthcoming Orthanc 1.4.3:  
[https://bitbucket.org/sjodogne/orthanc/commits/e02af4ca8003b1b5a80071a4b7c83ec6f1af23d7](https://bitbucket.org/sjodogne/orthanc/commits/e02af4ca8003b1b5a80071a4b7c83ec6f1af23d7)

Sébastien-

---

<div class="post-metadata">

### Author: ![Felix\_Nensa](https://discourse.orthanc-server.org/letter_avatar_proxy/v4/letter/f/fbc32d/32.png) [@Felix\_Nensa](https://discourse.orthanc-server.org/u/Felix_Nensa)
#### Post date: [November 29, 2018, 8:47pm UTC](https://discourse.orthanc-server.org/t/dicomweb-plugin/1218/5 "2018-11-29T20:47:35Z")

</div>

Perfect, thanks.
