48430 - Java plugin 1.3 runtime can not get proxy configuration for a url from browser of M17 build

Status: VERIFIED FIXED

(Core Graveyard :: Plug-ins, defect, P3)

Description

[Wen Li]

In M16 build, java plugin 1.3 runtime can get browser's proxy configuration for 
a specified url by nsPluginHostImpl::FindProxyForURL function. But in M17 
build, the nsPluginHostImpl::FindProxyForURL isn't even called when plugin 
instance try to find proxy for an url. From the java plugin console, we can 
know that plugin instance always uses 'no proxy' for all urls.

Comment 1

[Gervase Markham [:gerv]]

[e-mail] - I don't quite understand this report. Where are you saying 
the problem lies?

Gerv

Comment 2

[Gervase Markham [:gerv]]

Reporter says:

"I am not the person to write Java Plugin but I want to use
java plugin. I happened to know that the Java Plugin will
call the function findProxyForUrl to get the proxy configuration
if we don't set proxy manually. I tracked that in M16 build,
function nsPluginHostImpl::FindproxyForURL will be called as a
result. But in M17 build, it seems the function isn't called and
the java plugin always gets "no proxy".
Since Sun's Java Plugin 1.3 didn't change during these two builds,
I guess there is some change in Mozilla code leading this problem."

Gerv

Comment 3

[Gervase Markham [:gerv]]

Nominating for RTM - proxy support for Java.

Gerv

Comment 4

[ekrock's old account (dead)]

Wen, George: (a) What's the impact on developers/users of not fixing this bug
for Netscape 6 RTM? (b) Can Sun provide a resource to work on this? Andrei's
overburdened right now and I doubt he has the cycles to do this for RTM.

Comment 5

[av (gone)]

Ed, would you please look at this bug since as far as I remember you had similar 
problem with Proxy.

Comment 6

[Paul Williams]

In answer to [e-mail], what we were finding was that if you were 
viewing a web page containing a java applet, and you were connected to the web
server via a proxy server, then the java applet would not load, because the
plugin or the JVM was actually trying to pull in the applet (rather than the
browser doing this). Because only the browser seemed to know the proxy 
configuration, this applet-loading would fail. End result - no java works
if you're configured to use a proxy. These observations were made with M17
 - it didn't seem to be a problem in M16. The difference seemed to be that
in M16, nsPluginHostImpl::FindProxyForURL got called by the plugin 
(presumably on behalf of the JVM), but in M17 this call was never made.
So, in my opinion, it would be bad if Netscape 6 NTM still had this problem,
because your average corporate user who sits behind a proxy server would not
be able to run java applets.

Comment 7

[Gervase Markham [:gerv]]

Paul Williams - are you still seeing this on recent nightlies, either from the 
trunk or the branch?

Adding relnote-user to be sure...

Gerv

Comment 8

[Andrew Smith]

I can confirm this particular bug is fixed as of 0.8 and build 2001030110. The
Java plugin uses manually specified proxies when loading applets, although I
can't comment on anything specified by Proxy Auto Config as this has not been
fixed yet.

A remaining problem is that the Java plugin is ignoring the "no proxy for"
setting, which causes any applets on the near side of the proxy to fail when
loading. I've filled bug 70443 against this, but could do with someone
confirming it.

Comment 9

[Peter Lubczynski]

Marking FIXED as I thinik Ed Burns checked in something to fix this. 
Please re-open if you don't agree.

Comment 10

[shrirang khanzode]

since noone reopened this one..marknig VERIF.Reporter, pls reopen if u are not 
satisfied.Thx.