Plugin tries to use a SOCKS proxy even if there is none configured

[AndreasEhret]

This issue was imported from bugzilla with bugzilla2github

Bugzilla Bug Referenze: 846

Date: 2012-01-05 15:05:00 +0000
From: vogel
To: Lukasz Dracz <>
CC: nhb_web, omajid, unassigned

Last updated: 2014-08-06 15:32:23 +0000

Comment 4234

Date: 2012-01-05 15:05:00 +0000
From: vogel

Created attachment 632
Log from "javaws -verbose" when using direct internet connection

            I'm using icedtea-web-1.1.4, i. e. the icedtea-web-1.1.4-3.fc16.x86_64.rpm in Fedora 16, with the
            Firefox browser.

            The applet in question gets started properly via HTTP, regardless if using a proxy for HTTP or not. But
            shortly after the applet was started, it tries to open a TCP connection. This works, if the browser is
            configured for direct internet access, i. e. without a proxy.

            When configuring the browser to use a proxy for HTTP, HTTPS and GOPHER, but
            leaving the SOCKS proxy configuration empty (i. e. when there is no SOCKS proxy needed and available),
            the applet is not able to open this very same TCP connection, but fails instead.

            I've created a small shell script to run javaws (from icedtea-web) with the -verbose option and
            configured Firefox to use this script instead of /usr/bin/javaws. With this setup I created two log
            files, using the applet with and without a configured proxy, as described above. I'll attach these logs.

            The interesting part is after the line that says "Selecting proxy for:
            socket://platane-irmc.mgt.folz.de:80": When having no proxy for HTTP, then it says "Selected proxies:
            [DIRECT]", but when having a valid proxy for HTTP and an empty proxy configuration for SOCKS, it says
            nothing. This is the point where the TCP connection of the applet fails and the applet complains with an
            alert box containing: "java.lang.illegalArgumentException: port out of range:-2147483648"

            So, icedtea-web's javaws tries to use a SOCKS proxy when there is none configured, but when proxy
            configurations exist for other protocols. This is a bad idea, since there is no other option to say that
            there is no SOCKS proxy.

Attached file: log.direct.txt (text/plain, 17618 bytes)
Description: Log from "javaws -verbose" when using direct internet connection

Comment 4235

Date: 2012-01-05 15:06:28 +0000
From: vogel

Created attachment 633
Log from "javaws -verbose" when using a proxy for HTTP

Attached file: log.using_proxy.txt (text/plain, 17228 bytes)
Description: Log from "javaws -verbose" when using a proxy for HTTP

Comment 7212

Date: 2013-10-05 00:21:22 +0000
From: Omair Majid <>

I am not entirely clear on where this problem is. You mention both 'plugin' and 'javaws'. These are
completely different program and use different ways of obtaining the proxy.

            I suspect the problem with javaws was fixed by:
            http://icedtea.classpath.org/hg/icedtea-web/rev/c4476a810053

            But I don't see what could be wrong with the plugin. Could follow the steps on
            http://icedtea.classpath.org/wiki/IcedTea-Web#Filing_bugs and attach the logs for the plugin?

Comment 7264

Date: 2013-10-16 17:53:53 +0000
From: vogel

(In reply to comment #2)
> I am not entirely clear on where this problem is. You mention both 'plugin'
> and 'javaws'. These are completely different program and use different ways
> of obtaining the proxy.

            It's now 1.75 years later...

            AFAIR, with "plugin" I referred to the browser plugin that then uses javaws
            to start the app. When writing the title of the bug I didn't know which
            part of the setup is doing wrong, i. e. if it's the browser plugin that
            reads the proxy setup from the Firefox configuration, or if that is done
            by javaws, or if javaws does nonsense with a configuration read correctly
            by the browser plugin.

            >
            > I suspect the problem with javaws was fixed by:
            > http://icedtea.classpath.org/hg/icedtea-web/rev/c4476a810053
            >
            > But I don't see what could be wrong with the plugin. Could follow the steps
            > on http://icedtea.classpath.org/wiki/IcedTea-Web#Filing_bugs and attach the
            > logs for the plugin?

            Fedora 16 is long after EOL, and I've re-installed my computer with
            Linux Mint Debian Edition. This uses packages from Debian, the versions
            of the browser plugin and the javaws binary are:
            icedtea-6-plugin:amd64 1.3.2-1
            icedtea-netx:amd64 1.3.2-1

            I've so far not tried to test the error condition with LMDE, because I had
            to find my ways around this bug, and I use the workaround ever since. This
            means to use more than one browser, and have Firefox configured with no
            proxy, and working proxy settings in the other browsers.

            Should version 1.3.2 have the fix you mentioned? If so, then it would make
            sense to test again.

Comment 7276

Date: 2013-10-18 14:12:04 +0000
From: Andrew Azores <>

(In reply to comment #3)
> Should version 1.3.2 have the fix you mentioned? If so, then it would make
> sense to test again.

            If that particular changeset Omair linked is indeed the fix, then no, it would not be in 1.3.2. But
            could you check that 1.3.2 still exhibits this behaviour? Perhaps it was fixed by some other changeset
            since 1.1.4.