dicomweb-client: HTTP Error: 406 Client Error: Not Acceptable for url
Hello,
I get a client error when connecting to an azure dicom webserver. I can see normally all the records and I can as well remove a selected series from the DICOMweb server through Slicer’s extension. But when I try to “download and index” it I get:
DownloadSelectedSeries: Error in getting response from DICOMweb server.
HTTP Error:
406 Client Error: Not Acceptable for url: https://xxx-xxx.azurewebsites.net/studies/1.2.826.0.1.xxxxxx.x.xxx.x.x.xxxxxxxxxxx.xxxx.xxxx/series/1.2.826.0.1.xxxxxx.x.x.x.x.xxxx.xxx.xxxxx.xxxxxx/instances/1.2.826.0.1.xxxx.x.xxx.x.x.8xxxxx.xxx.xxxxxxxx.xxxxx
What could possibly go wrong?
OS: Win 10 Slicer version: 4.13.0-2021-03-03 r29745 / fca084e
Regards Antonios
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 20 (4 by maintainers)
@hackermd using
media_types=('application/dicom', )in client.retrieve_instance() fixes the issue for me! Thanks - I can use the latest version now!From an application perspective (e.g. to a user of Slicer’s DICOMwebBrowser extension) we would be looking for ways to make the code “just work” as often as possible without needing to know in advance that we wanted to be permissive or not. So I might expect the default behavior to be permissive. Unfortunately the end user often doesn’t control the server, or even if they administer the server they don’t have the ability to fix non-compliance. So they are relying on the application to handle as much as possible, meaning that the application developer wants to rely on the library developer to handle as much as possible. Unless it impacts performance or some other important thing the user probably doesn’t care that the server is not compliant.
Perhaps the library could provide a way to audit servers for compliance (something like
dciodvfydoes for instances). This would give a basis for helping server developers to improve compliance.Hi! I’m just seeing this for the first time. Apologies for missing it earlier. I’m working on the Azure DICOM implementation. Let me run this error to ground. Thanks for all the context in the posts above. Although @hackermd let us know about the problem early on.