Name: gm110360 Date: 02/01/2002


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

FULL OPERATING SYSTEM VERSION :
Microsoft Windows 2000 [Version 5.00.2195]



A DESCRIPTION OF THE PROBLEM :
Currently, the Java Plug-in only supports autoproxy config
files that end in .cnf or .js (ref:
http://java.sun.com/products/plugin/1.3/docs/proxies.html#Au
tomatic). However, many (large) companies use autoconfig
files that end in .cfg or that have no extension. This
makes configuring the Java Plug-in for users in these
companies much more difficult since the users must be
individually walked through the steps of manually
determining their proxy servers and specifying the servers
manually.


STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Access an applet using the Java Plug-in with an
autoproxy config file that does not end in .cnf or .js.


EXPECTED VERSUS ACTUAL BEHAVIOR :
I would expect the Plugin to be able to use an autoproxy
config, regardless extension; however, the actual behavior
is that the file cannot be interpreted.

This bug can be reproduced always.

CUSTOMER WORKAROUND :
Manually determine the proxy/SOCKS server from the
autoconfig file, and set the proxy in the Plug-in Control
Panel.
(Review ID: 139072)
======================================================================