jdk build b91 --> b92 regression, detected on Solaris and Linux.

JavaWS does not resolve host's local name returned by java.net.InetAddress.getHostName().

E.g. attempt to start "myapp.jnlp" from "myhost" on the same host
    javaws http://myhost/myapp.jnlp
fails with

    CouldNotLoadArgumentException[ Could not load file/URL specified: ... ]

the nested IOException contains confusing message:

    Server returned HTTP response code: 500 for URL: ...

That is not true: the HTTP server did not return that status code, because it did not recieve an HTTP request at all.

This issue raised if host's local names are presented in URLs from a jnlp file also.

(Please find actual stack traces for both the exceptions in Comments section)

Resolution for canonical fully-qualified host name or IP address works OK.
Posted Date : 2006-10-05 16:57:07.0

There is two reliable workarounds for that issue:
- never configure JavaWS to use browser's proxy settings, because it
  is not clear, which settings will take effect.
- don't set socks proxy in the browser which is used by javaws.
  This is another question - What is the default browser for javaws?

I believe this is just a proxy settings problem.

I have a test application at:

http://capoon.sfbay.sun.com:8080/test.jnlp

which simply connects to socket capoon.sfbay.sun.com:6000.

If you invoke "javaws http://capoon.sfbay.sun.com:8080/test.jnlp", it works.

If you invoke "javaws http://capoon:8080/test.jnlp" with proxy set to webcache.east.sun.com, it won't work, because webcache.east cannot resolve capoon hostname.  And you will get the exception as you see in this bug report.

If you use scaweb1.sfbay.sun.com instead, it works.

Or if you enable check box to bypass proxy for local address, it works too, because "capoon" is a local address.
Posted Date : 2006-10-05 18:52:52.0

If you want to use local hostname, you should either not use proxy, or use a proxy that can resolve the hostname.

I tried to run a few jnlp tck tests on windows XP and solaris-sparc with mustang b101.  Works great.

Please provide specific information and testcase to reproduce the problem.
Posted Date : 2006-10-05 23:29:19.0

changed synopsis to 

solaris/linux: JavaWS does not recognize the "default" browser

as this is the root cause of the problem, where we cannot locate the default browser and extract the correct proxy settings.
Posted Date : 2006-10-09 18:05:02.0

Removing regression keyword. As this is not a regression in real sense.
A behavior change. And a bug since the beginning for JavaWS.

Summary:
Problem: On unix (solaris/linux) JavaWS may fail in resolving addressess as it might fetch incorrect proxy settings.
Scenario details : Happens only on unix. When both mozilla and firefox installed. If proxy setting is correct in mozilla, but incorrect in firefox. (If user's system default is mozilla and they haven't checked to ensure firefox has correct proxy settings, this will be true.) JavaWS will fail in resolving addresses.

Why?
In unix there is no easy way to detect default system browser!
Java SE 6 JavaWS algorithm:
detect firefox proxy, if avail, use it.
otherwise detect mozilla proxy, use it
finally try netscape

Why isn't it a regression from 5.0?
5.0 JavaWS algorithm:
detect mozilla proxy, use it
finally try netscape

5.0 JavaWS user will encounter same issue(failure to resolve addressess) if mozilla, netscape are installed on unix. And mozilla does not have correct proxy settings.
Posted Date : 2006-10-28 00:34:17.0

hi am using a solaris sparc server and all of a sudden the internet browser refuse to load again any explanation for this pls help

i have just installes solaris 10 and am having a lot of trouble setting up the proxy settings for foxfire or any other brower mainly because i don,nt what i am doing. Please help me to set up the settings so i mayget online with solaris 10. my name is Earl Speir my emal is easyer67@verizon.net