Obtain metadata from OHIF and the API returns 400

Hello

I got the dist file via yarn run build Deploy on vps via nginx reverse proxy and install orthanc running on port 8042

now,I can see the studyList page, but I can’t access the image details

This is because when OHIF sends a request to obtain metadata, the interface returns 400

The following is the interface information and basic configuration
http:
https://treasure-x.top:3000/dicom-web/studies/1.2.840.86.755.86226839.811.1539260/metadata
response:
{
“Details” : “This WADO-RS plugin cannot generate the following content type: application/dicom+json, multipart/related; type=application/octet-stream; transfer-syntax=; transfer-syntax=”,
“HttpError” : “Bad Request”,
“HttpStatus” : 400,
“Message” : “Bad request”,
“Method” : “GET”,
“OrthancError” : “Bad request”,
“OrthancStatus” : 8,
“Uri” : “/dicom-web/studies/1.2.840.86.755.86226839.811.1539260/metadata”
}

app.config.js
{
namespace: ‘@ohif/extension-default.dataSourcesModule.dicomweb’,
sourceName: ‘dicomweb’,
configuration: {
friendlyName: ‘Orthanc Server’,
name: ‘Orthanc’,
wadoUriRoot: ‘/wado’,
qidoRoot: ‘/dicom-web’,
wadoRoot: ‘/dicom-web’,
qidoSupportsIncludeField: false,
imageRendering: ‘wadors’,
thumbnailRendering: ‘wadors’,
omitQuotationForMultipartRequest: true,
},
},

nginx:
server {
listen 3000 ssl;
server_name treasure-x.top:3000;

ssl_certificate /etc/letsencrypt/live/treasure-x.top/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/treasure-x.top/privkey.pem;
add_header Cross-Origin-Embedder-Policy "require-corp";
add_header Cross-Origin-Opener-Policy "same-origin";
root /ohif-viewer/dist;
index index.html; # 确保这行存在 
location /dicom-web {
    proxy_pass http://treasure-x.top:8042/dicom-web;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_redirect off;
    proxy_buffering off;
    add_header 'Access-Control-Allow-Credentials' 'true';
   add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';
   add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
   add_header 'Access-Control-Allow-Origin' '*';
}
location /wado {
   proxy_pass  http://treasure-x.top:8042/wado;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_redirect off;
    proxy_buffering off;
    add_header 'Access-Control-Allow-Credentials' 'true';
   add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';
   add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
   add_header 'Access-Control-Allow-Origin' '*';
}

}

orthanc dicomweb.json:
“DicomWeb” : {
“Enable”: true, // Whether DICOMweb support is enabled
“Root”: “/dicom-web”, // Root URI of the DICOMweb API (for QIDO-RS, STOW-RS and WADO-RS)
“EnableWado”: true, // Whether WADO-URI (aka. WADO) support is enabled
“WadoRoot”: “/wado”, // Root URI of the WADO-URI (aka. WADO) API
“Host”: “localhost”, // Hard-codes the name of the host for subsequent WADO-RS requests
“Ssl”: false // Whether HTTPS should be used for subsequent WADO-RS requests

}

It can be accessed at the address below
https://treasure-x.top:3000/

any thoughts?

thanks in advance

Hi,

Are you sure you are using the latest dicom-web plugin version ?

I can see this in the release notes:

HTH,

Alain.

Hello

I passed apt install orthanc-dicomweb go and download the plugin,
The HTTP request response is still the same
“Details” : “This WADO-RS plugin cannot generate the following content type: application/dicom+json, multipart/related; type=application/octet-stream; transfer-syntax=; transfer-syntax=”,

I’m not sure if the installed dicomweb plugin is up to date because version support isn’t provided

It’s very likely not the latest version. You may check it by calling

curl http://localhost:8042/plugins/dicom-web

Check this procedure to replace the packaged version by the LSB.

Latest version is 1.16: Orthanc downloads

HTH,

Alain

thank you very mush,

  • I successfully view the dicom image through the method you provided

thanks angin