Java Web Start parses proxy autoconfiguration scripts very naively.  It basically just greps for a "PROXY:" string and grabs the first proxy server it finds, without actually running the javascript logic.  We should consider a better solution.

N/A

fix for hopper
  xxxxx@xxxxx   2002-01-17

On Windows, we should grab the COM JScript parsing engine and use it to parse
the Javascript autoconfig script.  Unfortunately there is not much we can do
on Solaris/Linux, unless we bundle a Javascript parser with jaws.

  xxxxx@xxxxx   2002-07-23

Because of limitations of the J2RE proxy implementation, the above is not
possible for Mantis.  However, there are still steps that can be taken to
improve the proxy autoconfig script parsing implementation for Mantis:

1. Do not attempt to "guess" the proxy setting from an autoconfig script.  If
we encounter a script, we should prompt the user to enter a proxy, with the
"hint" being what we saw in the autoconfig script. 
2. Fix the Netscape 6 support so we now properly recognize an autoconfig setting
on Netscape 6.

  xxxxx@xxxxx   2002-10-15

What about using Rhino?

It even finds the proxy string if it is in a comment. I 
found this to be usefull for working around the problem 
with the current method of parsing the autoconfing script. 
I found where someone had posted this solution in the Java 
Web Start Forum.

http://forum.java.sun.com/thread.jsp?forum=38&thread=71651