United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
JDK-4924226 : PIT: Can not launch jnlp application via 127.0.0.1 address on the web server

Details
Type:
Bug
Submit Date:
2003-09-17
Status:
Resolved
Updated Date:
2003-10-10
Project Name:
JDK
Resolved Date:
2003-10-10
Component:
core-libs
OS:
solaris_9
Sub-Component:
java.net
CPU:
sparc
Priority:
P4
Resolution:
Fixed
Affected Versions:
5.0
Fixed Versions:
5.0 (tiger)

Related Reports
Relates:

Sub Tasks

Description
Can not launch jnlp application via 127.0.0.1 address on the web server.
All platforms.
Build: any Tiger build (/net/koori.sfbay/p/jdk03/jdk/1.5.0/all), starting from 
build 18.
Steps to reproduce:
- deploy any jnlp application in local http server
- try to download via: javaws http://127.0.0.1/path_to_application/test.jnlp
- exception coming:
java.io.IOException
	at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.jav
a:722)
	at com.sun.javaws.net.BasicNetworkLayer.doRequest(Unknown Source)
	at com.sun.javaws.net.BasicNetworkLayer.doGetRequest(Unknown Source)
	at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
	at com.sun.javaws.jnl.LaunchDescFactory.buildDescriptor(Unknown Source)
	at com.sun.javaws.Main.launchApp(Unknown Source)
	at com.sun.javaws.Main.main(Unknown Source)
Caused by: java.io.IOException: Server returned HTTP response code: 500 for URL: 
http://127.0.0.1:8080/nathanJavawsDev/ext_service/test_01.jnlp
	at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.jav
a:939)
	at 
java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:272)
	... 6 more
	
This is a regression starting from build18 (build17 is fine) 
/net/koori.sfbay/p/jdk03/jdk/1.5.0/all


                                    

Comments
CONVERTED DATA

BugTraq+ Release Management Values

COMMIT TO FIX:
generic
tiger

FIXED IN:
tiger

INTEGRATED IN:
tiger
tiger-b24


                                     
2004-06-14
EVALUATION

I am reasigning this to net group based on the following:
If I configure java web start with both 1.4.0 and tiger (deployment nightly build 9/28) and run tomcat on my ultra (gdisun.east) and attempt to access apps in my tomcat setup:
1.) if I load an app with <j2se version=1.4+ href="..."/> I will get the error shown.  In this case it will be running java 1.5.0 when it tries to download. (1.4+ results in the latest configured java at least 1.4)
2.) If I load the same app except with j2se version=1.4* href="..."/> It runs fine. (1.4* forces it to use some 1.4 version, in this case 1.4.0 is configured)
###@###.### 2003-09-20

------------------------------------

One change that happened in b18 is that we now force all http transactions
to go through the proxy (when a proxy is set). Formerly, if the connect
attempt through a proxy failed, then we retried with a direct connection.
This behavior was not documented, and was surprising in many respects.

The particular problem here is that the address 127.0.0.1 will never
be accessible via a proxy (hence the 500 error from the proxy).

I think the original behavior where we retry directly was wrong and the
correct thing to do, is to specify 127.0.0.1 in the list of non proxy
hosts.

###@###.### 2003-09-23

We will put in the special casing of loopback addresses to keep backward compatibility.

###@###.### 2003-10-07
                                     
2003-09-23



Hardware and Software, Engineered to Work Together