Pass the Proxy to the install4j Process That Downloads

Configure the install4j process that downloads the artifact. A Java property on the parent application does not automatically become a startup option of another JVM.

For the documented Java-networking path, a generated Unix installer can receive host/port before downloading through -J VM arguments:

./setup.sh -q -J-DproxyHost=proxy.example -J-DproxyPort=8080

Replace the filename and endpoint. For a permitted public-artifact download without proxy authentication, a candidate from the HTTP proxy list can supply the HTTP host and port in this Unix example. -q is unattended mode. Where required, the account inputs are proxyAuthUser and proxyAuthPassword; supply them through intended credential handling rather than shared logs.

On Windows, installer applications normally use native Windows networking and OS proxy configuration. Java properties do not configure that path. Selecting install4j.noWinInetConnection=true deliberately switches to Java networking, where those Java-side inputs can apply.

The Java path also recognizes JDK http.proxyHost/http.proxyPort and corresponding HTTPS properties. Hosts and ports are separate, and the destination URL remains unchanged.

Compiler downloads, including signing timestamps, belong to the build-time compiler's VM configuration. They do not establish the generated updater's later route. For interactive-versus-unattended differences, record executable, platform, transport and startup inputs before applying another version workaround.