search

ImagingDataCommons / slim

Interoperable web-based slide microscopy viewer and annotation tool
https://imagingdatacommons.github.io/slim/
Apache License 2.0
111 stars 36 forks source link

Configuration Issue #142

Open S-Streit opened 1 year ago

S-Streit commented 1 year ago

Short description: I try to change the dicom server thats within the local config towards using another ip so i can reach slim within the intranet using the ip. Loading of studies is okay, but once i open an image while loading bulkdata within api.js the url gets swapped towards localhost again and i really struggle to figure out why.

See related issue at the bottom would greatly appreciate help. Thanks in advance

image replacing localhost:8008 with the ip, which gets me past the first issue. After this however: image Somwhere, while fetching the image data, the IP gets replaced by localhost:8008 again. Everything works if localhost is exchanged with the IP.

Further i checked base url in DICOMwebmanager and other places so i cant really figure out why this happens.

Originally posted by @S-Streit in https://github.com/ImagingDataCommons/slim/issues/65#issuecomment-1448456237

hackermd commented 1 year ago

@S-Streit I think I know what's going on. It appears that the error occurs with the attempt to retrieve an ICC profile using the Retrieve Bulkdata resource. The URI for this resource is provided by the DICOMweb server in the DICOM metadata via the "BulkdataURI". It appears that the DICOMweb server includes URIs using "localhost" for host.

Do you have a reverse proxy in front of the DICOMweb server? If so, you need to configure the DICOMweb server such that it is aware of the proxy and includes the correct host in BulkdataURI values. Alternatively, you could rewrite the response message payload of search request messages.

S-Streit commented 1 year ago

This actually points me in the right direction and Slim is back in my TODO stack. I will see the DicomWebService config this or next week and give Feedback on the issue. Thank you very much for your time.

maxfscher commented 1 year ago

Just out of cusriosity, @S-Streit did you find a solution for your problem? I have an issue that expresses itself very similar.

S-Streit commented 11 months ago

Not yet, having other Problems writing different types on annotations ATM. Will actually come back. Probably it will involve reconfiguring the dicom server or use the suggested hack and replace the Request Payload. Did not look into it to hard since slims features are working to my needs at the moment.