-
Notifications
You must be signed in to change notification settings - Fork 47
Description
Line 1495 in bdb65e7
| "Content-Type": `multipart/related; type=application/dicom; boundary=${boundary}` |
In OHIF viewer the store measurements is failing when storing to DICOMlcoud server. see this issue for reference.
It has been traced and it was found to be caused by the server not recognizing the "Content-Type" header ( Built-in .NET library) because it is not formatted properly.
For STOW-RS, the Content-Type is being sent as:
Content-Type: multipart/related; type=application/dicom; boundary=2afeebaf-038d-792a-f952-d8e249ba8e96
The correct format should be:
Content-Type: multipart/related; type="application/dicom"; boundary="2afeebaf-038d-792a-f952-d8e249ba8e96"
Notice the "Quotation mark" around the type and boundary parameters: type="application/dicom"
This used to be a bug in the DICOM standard when DICOMweb was initially released but then they corrected it to match the HTTP RFC specs:
I think this is the new reference: http://dicom.nema.org/medical/dicom/current/output/html/part18.html#sect_8.7.3.5.1
and
https://tools.ietf.org/html/rfc2387
Related to this issue: dcmjs-org/dcmjs#113