Iced Tea Web OpenJDK - do not use Proxy

[AndreasEhret]

This issue was imported from bugzilla with bugzilla2github

Bugzilla Bug Referenze: 3690

Date: 2019-01-30 09:36:00 +0000
From: Milan <<milan.krause>>
To: JiriVanek <>
CC: axel.ahlborn, dbhole, sgehwolf, unassigned

Last updated: 2019-02-07 14:26:40 +0000

Comment 17281

Date: 2019-01-30 09:36:19 +0000
From: Milan <<milan.krause>>

We installed openjdk from redhat in version 1.8.0.191-1.b12 on server 2012 r2 and 2016 and try to
use the integrated icedtea webstart. Unfortunately, the call always tries directly access to the
internet without using the proxy settings. Is there an extra proxy setting option for the webstart
environment?

            Thanks in advance!

Comment 17282

Date: 2019-01-30 19:46:48 +0000
From: Severin Gehwolf <>

Is there a itweb-settings program? If so it should launch a GUI program which has a "Network" item.
There you should see various proxy related settings.

            Alternatively itweb-settings should be able to set this via a CLI:

            $ itweb-settings -list | grep proxy
            deployment.proxy.http.port: null
            deployment.proxy.auto.config.url: null
            deployment.proxy.https.host: null
            deployment.proxy.override.hosts: null
            deployment.proxy.socks.port: null
            deployment.proxy.socks.host: null
            deployment.proxy.bypass.local: null
            deployment.proxy.http.host: null
            deployment.proxy.https.port: null
            deployment.proxy.same: false
            deployment.proxy.ftp.port: null
            deployment.proxy.bypass.list: null
            deployment.proxy.type: 3
            deployment.proxy.ftp.host: null

            Then for example:
            $ itweb-settings -set deployment.proxy.http.port 88

            HTH

Comment 17283

Date: 2019-01-31 08:58:48 +0000
From: Axel Ahlborn <<axel.ahlborn>>

Hello Severin,
unfortunately we had the same problems as described in this bug. By starting a jnlp based Java
Application from a webserver we noticed different behaviours of ITW by using a Proxy or not and when
using a Proxy, what Kind of settings where used and where did they come from ? The difference between
the tests: Firefox Browser was installed - or not.
Next Topic was Java Code Signing Certificate Set Up. When you install a third Party application that is
using a Certificate from en external vendor you need
right one proxy settings for OCSP, CRL´s and all things included in this certificate that match to a
source in the WWW behind your own proxy.

            So before starting ITW in our production we had to clarify the following open points:

            Changes for exceptions.sites functionality
            Changes to netx/net/sourceforge/jnlp/tools/CertInformation.java
            Changes to netx/net/sourceforge/jnlp/tools/JarCertVerifier.java
            Changes for reading Proxy Settings
            Changes to disable Widget Settings in Control Panel
            Add Site Exception Viewer to Control Panel

            To integrate all the changes we did I startet Bug #3684.

            Greetings Axel

Comment 17284

Date: 2019-01-31 10:11:52 +0000
From: Milan <<milan.krause>>

Hi Severin,

            thank you for the fast response.
            We installed the newest version from redhat openjdk on windows on which these itweb-settings programs do
            not seem to exist. Is it right?

Comment 17285

Date: 2019-01-31 10:50:19 +0000
From: Severin Gehwolf <>

(In reply to Axel Ahlborn from comment #2)
> The difference between
> the tests: Firefox Browser was installed - or not.

            That makes some sense. The default proxy settings seem to be to use the default browser settings.

Comment 17286

Date: 2019-01-31 10:52:59 +0000
From: Severin Gehwolf <>

(In reply to Milan from comment #3)
> We installed the newest version from redhat openjdk on windows on which
> these itweb-settings programs do not seem to exist. Is it right?

            Apparently there is no direct launcher for windows yet. The cmd-line on Linux is something like this:

            /usr/lib/jvm/jre-1.8.0-openjdk/bin/java
            -Xbootclasspath/a:/usr/share/icedtea-web/netx.jar:/usr/share/icedtea-web/plugin.jar:/usr/share/icedtea-web/jsobject.jar:/usr/share/java/tagsoup.jar:/usr/lib/jvm/jre-1.8.0-openjdk/lib/ext/nashorn.jar
            -Xms8m -classpath /usr/lib/jvm/jre-1.8.0-openjdk/lib/rt.jar:/usr/lib/jvm/jre-1.8.0-openjdk/lib/jfxrt.jar
            -Dicedtea-web.bin.name=itweb-settings.itweb -Dicedtea-web.bin.location=/usr/bin/itweb-settings.itweb
            net.sourceforge.jnlp.controlpanel.CommandLine

            Provided you know the location of jars on your system you might be able to hand-craft your own to launch
            the tool.

Comment 17287

Date: 2019-01-31 12:10:42 +0000
From: Axel Ahlborn <<axel.ahlborn>>

hi Severin, that can be discussed if a direct launcher for Windows is part of icedtea-web. Of
course, you have no other Chance to use ITW for Windows by using a direct launcher. Our solution is a
mix included into the ITW Sourcecode and included into the Setup of our OpenJDK Runtime, OpenJFX8u and
ITW.

            - Read Proxy Settings from Registry (Yes, there are DWords....)
            - Define a Mimetype JNLP for IE
            - Define the behaviour for the System to Launch JNLP / JNLPS
            - Take the Start Code for ITW, put it into Powershell and Compile as EXE.

            Greetings Axel

Comment 17288

Date: 2019-02-02 08:57:34 +0000
From: JiriVanek <>

Hi!

            I need to fix few statement sin this thread.
            - adding Deepak, as this have something to do with not-upstream launcher used in redhat MSIs
            - ITW is not taking proxy from default browser. it is indeed, as Axel noted - taking only Firefox's
            proxy setings. Not nice. But there was not different browser for linux for ages.
            - itweb settings (or controlpanel) have indeed to select proxy - none, firefox, custom. For you, the
            custom one or none should be a solution. If it is on none, and still takes FF proxy, then it is bug.
            - unluckily, in MSIs from RH are not-upstreamd custom binary launchers which Alex included against all
            of us, with (probablyu corrrect) asusmption that .bat files cant be integrated in windows correctly.
            This actually evoked the the creation of native launchers for upstream ITW 1.8.
            - If you are unable to locate itwebsettings or controlpanel, in those MSIs, please, create
            https://bugzilla.redhat.com/. In meantime, cna you try upstream ITW? It should allow you to configure
            proxy, and any config it creates, should be directly usable by ITW from MSIs you wish to use.

            Sorry for confussion

Comment 17297

Date: 2019-02-07 06:08:15 +0000
From: JiriVanek <>

Hi Axel/Milan!

            Is this issue blocked on me, or on your side? If on mine, what do you wish me to do?

Comment 17301

Date: 2019-02-07 07:50:41 +0000
From: Milan <<milan.krause>>

Sorry, I was not in the office in the last days.
The problem is still acute and I honestly do not quite understand what you want me to do. Proxy settings
on Windows of Firefox are ignored in my ICW. I also tried it with various environmental variables, but
which do not work. Where can i set the itweb settings, i have no controlpanel?

Comment 17303

Date: 2019-02-07 14:26:40 +0000
From: JiriVanek <>

I would go with following:
Download one of http://icedtea.wildebeest.org/download/icedtea-web-binaries/1.7.1/windows/

            Make it work :)

            In that, you should have itweb-settings.bat
            That *should* be configuring same deployment.properties, as *yours* *current* javaws is reading. You
            will most likely find, that in network, is checked out "use browser settings" select "none" and
            apply/ok. Then you can verify that your deployment.properties file contais deployment.proxy.type=0
            (as from: itweb-settings --verbose --help | grep deployment.proxy.type
            itweb-settings -reset deployment.proxy.type - Resets the value of `deployment.proxy.type` setting.
            deployment.proxy.type - 0 (default: 3) (Possible: are in range -1 to 3 (inclusive))
            )


            HTH