Name: gm110360 Date: 04/17/2002


FULL PRODUCT VERSION :
java version "1.4.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92)
Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode)

FULL OPERATING SYSTEM VERSION :Windows NT Version 4.0


EXTRA RELEVANT SYSTEM CONFIGURATION :
IE 4, 5, and 6 affected

A DESCRIPTION OF THE PROBLEM :
The JPI implements the javascript functions isResolvable,
dnsResolve, and isInNet in order to support Proxy Auto-
configuration (.pac) files. The JPI does not fully
implement these functions as they do not support forward
dns lookups ( name to IP ). As we operate in a proxy
environment and have many machines both external and
internal that use a common domain name, we rely heavily on
these functions in order to send traffic direct for
internal sites and to the proxies for external traffic.

As the number of external IP address segments we have are
limited and are not changed very often, while new box names
can occur very frequently, we have implemented something
like the following.

Assuming an external address segment of
a.b.c.0/255.255.255.0 and a domain name "acme.com" that is
used for both external and internal machines:

function FindProxyForURL(url, host)
{
    if ( dnsDomainIs( host, "acme.com" ) )
    {
        if ( isInNet( host, "a.b.c.0", "255.255.255.0" ) )
            return "PROXY proxy:8080";
        else
            return "DIRECT"
    }
}

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Implement a PAC file similar to the one given
2. Point 1.4 JPI to this new PAC file
3. Try to access and external site by hostname. As
isInNet will return false, the JPI will try to go direct.

EXPECTED VERSUS ACTUAL BEHAVIOR :
Expected these functions to perform forward DNS lookups.
As this .pac file works for the thousands of browser
installations we have, I expected to be able to use the
same .pac file for the JPI. This .pac file works for IE,
Netscape, and for the Microsoft JVM.

ERROR MESSAGES/STACK TRACES THAT OCCUR :
JPI reports that no class definition was found as the connection attempt failed.

This bug can be reproduced always.
(Review ID: 145122)
======================================================================