-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong media type for Retrieve Instance transaction #444
Comments
Thank you, @hackermd ! That certainly simplifies the retrieve transactions and makes all of them consistent with each other. We're looking into this now, and it certainly makes sense. Thanks! We'll keep you posted here. |
Great! Thanks for looking into it @StevenBorg |
@hackermd After some discussion, our take is that we should adopt the newer framework, even prior to acceptance under the standard, while still maintaining backward compatibility (in this case) for APIs which might be using the current standard. Do you see any concerns with this approach? |
No concerns. I agree that this would be the best approach. The "newer" framework has actually always been the standard - at least it was supposed to. The goal of Supplement 183 was to refactor the documentation of Part 18 without actually changing the behavior. Unfortunately, a few things got broken and we are currently trying to correct those. However, since Supplement 183 was officially accepted, we should probably consider |
Issue is fixed. Closing |
Describe the bug
The Retrieve Instance transaction of the DICOMweb service uses the wrong media type. It should be
multipart/related; type="application/dicom"
instead ofapplication/dicom
. See DICOM Correction Proposal 2040 for clarification.The text was updated successfully, but these errors were encountered: