As best I can tell, there isn’t any way to get the desktop client to use a proxy at this point. The underlying frameworks–node.js and Electron–are a little weird about controlling behavior via environment variables because, by their nature, it can be hard to determine what the environment is. The library that the desktop client uses for HTTP/REST calls lets you configure an HTTP agent that can include, amongst other things, a proxy configuration, but that requires explicit coding to support that and that’s not in there. I created an issue for this, so hopefully this is something that can get into an upcoming release.
--
Rick Herrick
XNAT Architect/Developer
Computational Imaging Laboratory
Washington University School of Medicine
From:
'Jerico Revote' via xnat_discussion <xnat_di...@googlegroups.com>
Date: Thursday, March 17, 2022 at 3:53 PM
To: xnat_discussion <xnat_di...@googlegroups.com>
Subject: [XNAT Discussion] XNAT Desktop Client | HTTP/Web Proxy
|
* 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/378bf1c0-0075-4be9-9826-ade499315c5dn%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.