Orthanc with DicomWEB plugin behind a reverse-proxy

Google Groups archive
1

Good evening,

I use the DicomWEB front end of an Orthanc server behind a reverse proxy. Before transmitting DicomWEB requests, the proxy adds the X-Forwarded-Host and X-Forwarded-Proto headers to the request headers (verified). But, it seems that these headers are ignored by the plugin.

The BulkDataURI or RetrieveURL attributes do not undergo any transformation…

Orthanc version : 1.11.3
DicomWEB plugin version : 1.13

Any ideas ?

2

Hi Didier,

This DicomWeb configuration should handle that:

    "PublicRoot": "/dicom-web/", // The public Root URI of the DICOMweb API in case it is different from "Root".
                                 // This is useful if, e.g, your Orthanc is behind a reverse-proxy and has another
                                 // base endpoint than the "Root" one.  Note that, if using a reverse-proxy, make sure to set the "host"
                                 // and "proto" correctly in the "Forwarded" HTTP headers.
                                 // (since release 1.8)

I have just tried it in this sample https://bitbucket.org/osimis/orthanc-setup-samples/src/master/docker/nginx/

curl --request GET “http://demo:demo@localhost/orthanc/dicom-web/studies/1.2.276.0.7230010..../metadata” --header “Accept: application/dicom+json” | grep Bulk

“BulkDataURI” : “http://localhost/orthanc/dicom-web/studies/1.2.276.0.7230010….”

HTH,

Alain

3

Hi Didier,

I have now solved this in this commit: orthanc-dicomweb: 862a0370801f

Note that, with the current version, you can use the “Forwarded” header:
'forwarded': 'host=my-domain;proto=https'

Best regards,

Alain.