Hi Alex,
I looked into this a bit. DICOM uses TCP for its underlying transport protocol. Open-source NGINX only supports proxying HTTP, with TCP proxying supported by NGINX Plus release 5 or later. If you have or can get a license for NGINX Plus, you could set up TCP proxying as described in that documentation.
If there’s an FOSS TCP proxy service available, I don’t know what it is. If you find one, I’d love to hear about it! Two possible solutions are:
Outside of a TCP proxy, the only other solution I can think of is opening the desired port for DICOM composite operations on the firewall and routing that directly to the Tomcat server. IT folks love that sort of thing so it shouldn’t be a problem 😉
--
Rick Herrick
Sr. Programmer/Analyst
Neuroinformatics Research Group
Washington University School of Medicine
Phone: +1 (314) 273-1645
From:
xnat_di...@googlegroups.com <xnat_di...@googlegroups.com>
Date: Friday, October 16, 2020 at 4:19 PM
To: xnat_discussion <xnat_di...@googlegroups.com>
Subject: [XNAT Discussion] Proxy for DICOM receiver
|
* External Email - Caution * |
--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
xnat_discussi...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/xnat_discussion/6bd82cbf-74de-43a9-8440-8aa525008398n%40googlegroups.com.
The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.