[Bug 1474] Can't get javaws to use SOCKS proxy

Sat Oct 5 15:29:11 PDT 2013

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

--- Comment #3 from silvrax <silvrax at gmail.com> ---
I've just tested this with the latest sources. If I put the following in my
deployment.properties then I can get my application to work properly:

deployment.proxy.socks.port=8989
deployment.proxy.socks.host=localhost
deployment.proxy.type=1
deployment.security.level=ASK_UNSIGNED

I can see that when it tries to download the first file, it selects the SOCKS
proxy, and then attempts to download the logo file:

All possible urls for location=http://10.148.0.16:80/images/logo.gif
state=CONNECTING DOWNLOAD STARTED : [http://10.148.0.16:80/images/logo.gif,
http://10.148.0.16:80/images/logo.gif]
Selecting proxy for: http://10.148.0.16:80/images/logo.gif
Selected proxies: [SOCKS @ localhost/127.0.0.1:8989]
For location=http://10.148.0.16:80/images/logo.gif state=CONNECTING DOWNLOAD
STARTED the server returned 302 code for HEAD request for
http://10.148.0.16:80/images/logo.gif

The fact that I get a 302 is probably correct for this particular application.
After this I can see it successfully pulling in some jar files and then it
launches correctly.

So far so good, basically my problem is solved, so thank you for that!

I've also tried with the following deployment.properties:

deployment.proxy.http.host=localhost
deployment.proxy.socks.port=8989
deployment.proxy.socks.host=localhost
deployment.proxy.type=1
deployment.proxy.http.port=8989
deployment.security.level=ASK_UNSIGNED

I then get the following in my logs. It does suggest it will try both the HTTP
and SOCKS proxy. But I only see it trying (and failing) to use the HTTP proxy.

All possible urls for location=http://10.148.0.16:80/images/logo.gif
state=CONNECTING DOWNLOAD STARTED : [http://10.148.0.16:80/images/logo.gif,
http://10.148.0.16:80/images/logo.gif]
Selecting proxy for: http://10.148.0.16:80/images/logo.gif
Selected proxies: [HTTP @ localhost/127.0.0.1:8989, SOCKS @
localhost/127.0.0.1:8989]
While processing http://10.148.0.16:80/images/logo.gif by HEAD for resource
location=http://10.148.0.16:80/images/logo.gif state=CONNECTING DOWNLOAD
STARTED got java.net.SocketException: Unexpected end of file from server: 
java.net.SocketException: Unexpected end of file from server
        at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:772)
        at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:633)
        at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:769)
        at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:633)
        at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1323)
        at
java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:468)
        at
net.sourceforge.jnlp.cache.ResourceTracker.getUrlResponseCode(ResourceTracker.java:862)
        at
net.sourceforge.jnlp.cache.ResourceTracker.findBestUrl(ResourceTracker.java:899)
        at
net.sourceforge.jnlp.cache.ResourceTracker.initializeResource(ResourceTracker.java:781)
        at
net.sourceforge.jnlp.cache.ResourceTracker.processResource(ResourceTracker.java:621)
        at
net.sourceforge.jnlp.cache.ResourceTracker.access$500(ResourceTracker.java:77)
        at
net.sourceforge.jnlp.cache.ResourceTracker$Downloader$1.run(ResourceTracker.java:1154)
        at
net.sourceforge.jnlp.cache.ResourceTracker$Downloader$1.run(ResourceTracker.java:1152)
        at java.security.AccessController.doPrivileged(Native Method)
        at
net.sourceforge.jnlp.cache.ResourceTracker$Downloader.run(ResourceTracker.java:1152)
        at java.lang.Thread.run(Thread.java:724)

After this, I see several similar exceptions when it's trying to pull in the
jar files and then it bails out.
So this has me left wondering, is this supposed to happen? Note that in this
case, the HTTP proxy is set to the address/port where the SOCKS proxy is
actually listening. So if it's first trying to use the HTTP proxy, that is
expected to fail. But shouldn't it then try to use the SOCKS one?

I did another test where I've changed the HTTP proxy port to 8990, where
nothing is actually listening. In that case I do see it first attempting the
HTTP proxy and throwing a connection refused exception, to then try again using
the SOCKS proxy, which works.

So, to summarize, my application works using these two settings:

deployment.proxy.socks.port=8989
deployment.proxy.socks.host=localhost
deployment.proxy.type=1
deployment.security.level=ASK_UNSIGNED

or:

deployment.proxy.http.host=localhost
deployment.proxy.socks.port=8989
deployment.proxy.socks.host=localhost
deployment.proxy.type=1
deployment.proxy.http.port=8990
deployment.security.level=ASK_UNSIGNED

But it doesn't when these are used:

deployment.proxy.http.host=localhost
deployment.proxy.socks.port=8989
deployment.proxy.socks.host=localhost
deployment.proxy.type=1
deployment.proxy.http.port=8989
deployment.security.level=ASK_UNSIGNED

I realize one could argue that this new "problem" is just a case of
misconfiguration, but I'm just wondering if the observed behavior is what was
intended to happen?

Thanks again for looking in to this case.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/distro-pkg-dev/attachments/20131005/bc61879a/attachment.html 