Markus D. Herrmann

@sedghi would you like to draft a pull request?

I have run some tests against a range of different archives and the requests appear to handled just fine when the quotes are omitted. Therefore, I would be open to...

I like the `auto` option @pieper. If the current behavior in fact violates the HTTP standard, then I tend argue that we should not keep it as default.

@GitanjaliChhetri @fedorov got the status checks working.

Thank you for reporting the issue @Zaelot. It appears the location of the website has changed. It is now located at https://www.dicomstandard.org/using/dicomweb.

There are two things that could pose problems for backwards compatibility: 1. A change of *Code Meaning*. This appears to happen relatively frequently. It is important to consider in this...

cc @dclunie for awareness

@MathisGuilhin reported: > When I use `retrieveSeries` or `retrieveStudy`, only the first instance of DICOM is readable. > It actually gives back a list of instances as arraybuffers, but only...

@swederik could this be the problem? https://github.com/dcmjs-org/dicomweb-client/blob/f0b3086a12b0aa68f0f100d485fe224095be97b9/src/message.js#L192

[RFC1872 The MIME Multipart/Related Content-type Section 3.4 Syntax](https://www.rfc-editor.org/rfc/rfc1872.html#section-3.4) states: > Note that the parameter values will usually require quoting. As pointed out by @Zaid-Safadi, all examples in the RFC for...