Remark 1: The following configuration options were present in Utf8 if you are dealing with an international environment. It might be a good idea to set this option to and 'proto' correctly in the 'Forwarded' HTTP headers.įurthermore, the global option DefaultEncoding specifies theĮncoding (specific character set) that will be used when answering a Note that, if using a reverse-proxy, make sure to set the 'host' This is useful if, e.g, your Orthanc is behind a reverse-proxy and has another 'PublicRoot': '/dicom-web/', // The public Root URI of the DICOMweb API in case it is different from 'Root'. 'SeriesMetadata' : 'Full', // How series-level metadata is retrieved (since release 1.1, cf. 'StudiesMetadata' : 'Full', // How study-level metadata is retrieved (since release 1.1, cf. from the reverse-proxy 'forwarded' headers. If empty (default), the plugin will guess it from other configurations or 'Host' : '', // Hard-codes the name of the host for subsequent WADO-RS requests. 'QidoCaseSensitive' : true, // For QIDO-RS server, whether search is case sensitive (since release 0.5) If Orthanc is behind a reverse-proxy, the 'forwarded' headers will be used instead of the config. 'Ssl' : false, // Whether HTTPS should be used for subsequent WADO-RS requests.

'WadoRoot' : '/wado', // Root URI of the WADO-URI (aka. 'EnableWado' : true, // Whether WADO-URI (previously known as WADO) support is enabled 'Root' : '/dicom-web/', // Root URI of the DICOMweb API (for QIDO-RS, STOW-RS and WADO-RS) 'Enable' : true, // Whether DICOMweb support is enabled

Osirix dicom are password protected