[Bug] An error is reported for obtaining metadata

[Greyxy]

Describe the Bug

I deployed ohifviewer and orthanc on vps Reverse proxy via nginx The interface on the home page of OhifViewer is normal, and the interface response code is 400 when obtaining metadata

Steps to Reproduce

1.Enter OhifViewer via the IP+ port 2.Open the browser console 3.click basic viewer

The current behavior

{ "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.3.46.670589.11.2400602835.1460368295.1915225765.623499641/series/1.3.46.670589.11.2828603849.3733095346.343344967.1033070319/metadata" } nginx.conf server { listen 3000 ssl; server_name localhost: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://localhost:8042;
    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://localhost:8042;
   proxy_set_header HOST $host;
   proxy_set_header X-Real-IP $remote_addr;
   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' '*';
}

}

app-config.js { namespace: "@ohif/extension-default.dataSourcesModule.dicomweb", sourceName: "dicomweb", configuration: { friendlyName: "treasure", name: "treasure", wadoUriRoot: "/wado", qidoRoot: "/dicom-web", wadoRoot: "/dicom-web", qidoSupportsIncludeField: !1, imageRendering: "wadors", thumbnailRendering: "wadors", enableStudyLazyLoad: !0, supportsFuzzyMatching: !1, supportsWildcard: !0, staticWado: !0, singlepart: "bulkdata,video", bulkDataURI: { enabled: !0, relativeResolution: "studies" }, omitQuotationForMultipartRequest: !0, }, }, 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" : "treasure-x.top", // Hard-codes the name of the host for subsequent WADO-RS requests "Ssl" : true // Whether HTTPS should be used for subsequent WADO-RS requests }

The expected behavior

An interface error is causing me to be unable to view DICOM images

OS

ubuntu20

Node version

16.20.1

Browser

chrome:latest

[sedghi]

I'm having trouble following the reproduction steps. Could you possibly share a mini repository or something similar?

[Greyxy]

我在执行复制步骤时遇到问题。你能共享一个迷你存储库或类似的东西吗？

1.I packaged ohif viewer with yarn build and apt install orthanc

2. I reverse proxy orthanc through nginx, and the configuration information is given above
4. Currently I can access ohif on port 3000 and get the data uploaded to orthanc
6. When I want to view the image, the request metadata interface is abnormal and has given an exception message
8. You can check the error at https://treasure-x.top:3000
10. Attached are the configurations related to dataSource, nginx, orthanc-dicomweb

11. configurations.txt

thanks in advance

[Greyxy]

我在执行复制步骤时遇到问题。你能共享一个迷你存储库或类似的东西吗？

If you access the connection I provided, orthanc's default login password is' orthanc '.

[Greyxy]

I found that the reason is because the version of the orthanc-dicomweb plugin is not the latest 1.16, which makes it unparse: application/dicom+json, multipart/related; type=application/octet-stream; transfer-syntax=; transfer-syntax="header