dcm4che / dcm4chee-arc-light

DICOM Archive J2EE application
438 stars 242 forks source link

Dicom files are not opening in weasis when click on view button of studies in dcm4chee ui #4592

Open abdullah951 opened 1 week ago

abdullah951 commented 1 week ago

Screenshot 2024-10-24 203259

IID_STUDY_URL=weasis://$dicom:rs --url "http://192.168.88.57:8080{{qidoBasePath}}" -r "studyUID={{studyUID}}" --query-ext "&includedefaults=false"

IID_URL_TARGET=_self

IID_PATIENT_URL=weasis://$dicom:rs --url "http://192.168.88.57:8080{{qidoBasePath}}" -r "patientID={{patientID}}" --query-ext "&includedefaults=false"

It was working two days ago

ifaisalshahzad commented 4 days ago

Recent changes in Chrome version 130.0.6723.59 and later, have affected how custom URL protocols like weasis:// are handled. This is causing issues with launching Weasis from DCM4CHEE. Chrome's new behavior:

Potential solutions: Modify the Weasis launch URL to comply with Chrome's new rules, use URL encoding for special characters (e.g., replace spaces with %20)

as per weasis article To build an URI (weasis://path) without weasis-pacs-connector, you must choose one or more commands, encode the commands, and add the scheme weasis://

Problem Statement: when encoding url as following and updating in DCM4CHEE IID_STUDY_URL=weasis://$dicom%3Ars+--url+"https%3A//192.168.1.114:8080{{qidoBasePath}}"+-r+"studyUID={{studyUID}}"+--query-ext+"&includedefaults=false" image

after updating above, when navigating to view study, url getting encoded again as follows weasis://$dicom%253Ars+--url+%22https%253A//192.168.1.114:8080/dcm4chee-arc/aets/DCM4CHEE/rs%22+-r+%22studyUID=1.3.6.1.4.1.5962.99.1.2786334768.1849416866.1385765836848.3.0%22+--query-ext+%22&includedefaults=false%22

how to stop DCM4CHEE encoding or handling the colon(:) encoding problem raised by chrome

Urgently waiting for community solution.