[BUG] Mirth Connect Administrator Launcher not using http proxy configuration for OCSP requests

[nicovn]

Describe the bug
The actual launch (launch.exe) is not using the HTTP proxy settings configured in the popup window at startup of the launcher.exe application.

Even when yo configure a http(s) proxy in the launcher application it is not used by the launch process for e.g. the OCSP requests towards ocsp.digicert.com

To Reproduce
Setup launcher to use a http proxy
Launch the Administrator of a mirth installation, and you'll see that the OCSP requests (verifying jar file...) are not sent through the HTTP proxy, but are using a direct connection.

Expected behavior
The http proxy that you setup is used for all HTTP/HTTPS requests

Workaround(s)
I haven't found a workaround yet ...