Fails to display image over WADO-RS

[yangszwei]

Environment

• Bluelight is hosted on Ubuntu with Docker
• Google Chrome on macOS 131.0.6778.86 (Official Build) (arm64)

Configuration

bluelight/data/config.json

{
    "DICOMWebServersConfig": [
        {
            "AETitle": "RACCOONQRSCP",
            "QIDO-enableHTTPS": false,
            "WADO-enableHTTPS": false,
            "QIDO-hostname": "REDACTED",
            "WADO-hostname": "REDACTED",
            "QIDO-PORT": 8081,
            "WADO-PORT": 8081,
            "contentType": "application/json",
            "timeout": 80000,
            "charset": "UTF=8",
            "QIDO": "dicom-web",
            "WADO-URI": "wado",
            "WADO-RS": "dicom-web",
            "WADO-RS/URI":"RS",
            "STOW": "stow",
            "enableRetrieveURI": false,
            "includefield": false,
            "enableXml2Dcm":false,
            "Xml2DcmUrl":"/upload",
            "target": "http://REDACTED/bluelight/html/start.html",
            "token": {
                "apikey":"",
                "bearer":""
            }
        }
    ]
}

Description

When the viewer is configured to retrieve DICOM images via WADO-RS, the viewer breaks with the error message:

Uncaught dicomParser.readPart10Header: DICM prefix dicomParser.js:17173 not found at location 132 - this is not a valid DICOM P10 file.

But, If the "WADO-RS/URI" is set to "URI" instead, the image can render correctly.

[cylien]

This requires information about the connected PACS server, e.g., the Raccoon configuration.

Does the DCM4CHEE have this issue?

[cylien]

This issue was caused by putting the source code of BlueLight in Raccoon without recompiling. Put the source code in Raccoon and re-compile the Raccoon, and then this problem will be solved.