[Bug 846] New: Plugin tries to use a SOCKS proxy even if there is none configured

[bugzilla-daemon at icedtea.classpath.org]

http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=846

             Bug #: 846
           Summary: Plugin tries to use a SOCKS proxy even if there is
                    none configured
    Classification: Unclassified
           Product: IcedTea-Web
           Version: unspecified
          Platform: x86_64
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P3
         Component: Plugin
        AssignedTo: dbhole at redhat.com
        ReportedBy: vogel at folz.de
                CC: unassigned at icedtea.classpath.org


Created attachment 632
  --> http://icedtea.classpath.org/bugzilla/attachment.cgi?id=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.

-- 
Configure bugmail: http://icedtea.classpath.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.