JDK-4988192 : Java Plugin 1.4.2 does not allow applet to query proxy info. from browser settin
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 1.4.2,1.4.2_03
  • Priority: P4
  • Status: Closed
  • Resolution: Not an Issue
  • OS: solaris_2.6,windows_2000
  • CPU: x86
  • Submitted: 2004-02-04
  • Updated: 2004-05-03
  • Resolved: 2004-05-03
Related Reports
Relates :  
Relates :  
Description
Netlet(applet) component of Portal server needs proxy info. from browser
settings to be able to establish secure TCP/IP tunnels. IE is  using plugin
with "Use Browser Settings" set to true under "Proxies" in the plug-in Control
panel. And IE browser contains a pac file with the proxy info. The plug-in
Control panel does not have any content in the proxy or pac file fields.

Attempt to read the Browser Settings directly from the applet, results in
Security exceptions. And there is no way to get this proxy info. from the
plug-in either. (no fecility to query this info. via any exposed api)

Wihtout the plug-in we could query browser settings directly from the applet.
However when using plug-in the applet cannot get browser setting info.
(Either from the browser directly or from the  plug-in.)

This causes a regression on our software when customers use Java Plugin
with "Use Browser Settings" set to true.

We need the applet to somehow be able to query this proxy info.

Comments
EVALUATION The customer is using Microsoft private package com.ms.lang.* and com.ms.security.*. It is not shipped with Sun's JRE. If the customer wants to use that, they can ship the jar file from Microsft (I don't know whether they can do that) and put into the bootclasspath enviroment variable. Also if any native library needs to be loaded as well, they need to put the library path into the java.library.path enviroment variable. Anyway, publish proxy API from plug-in requires a RFE and probably a JSR. In this case, even we publish the API, the user's code needs to be changed. A suggestion/workaround is the applet writer can implement the logic (reading from registry) themselves by using JNI call to read from Windows registry. That may require user's code to be signed based on Java security model. So I don't think this is our bug. ###@###.### 2004-02-04
04-02-2004