With a manually configured proxy, Java ignores the "no proxy for" setting when loading applets. In other words, it uses the manually configured proxy for all connections, even if the "no proxy for" setting specifies otherwise. This tends to cause the applet to fail while loading. I have a suspicion that this might be related to bug 16677. For example, if ".foo.com" is the "no proxy for" setting, the Java console (running at trace level 2) display this: Applet Installation finished. Opening http://www.foo.com/bar.class Connecting http://www.foo.com/bar.class with proxy=webproxy:80 java.security.AccessControlException: access denied (java.net.SocketPermission webproxy resolve) It then goes on to give a large stack dump. It should say "with no proxy".

Reassigning to OJI. Ed, if this is confirmed, it means bug 48336 was not correctly fixed (as the last comment in that bug suggested) reporter what build are you using plz?

I'm using 0.8 on Win95. I wasn't convinced that this problem was the same as bug 48336. I thought that referred to Java ignoring the settings completely. Here, it is picking up the proxy setting and using it, but ignoring the "no proxy for" part. So, we're one step on, but it's still broken for people who want to access applets that are behind the proxy. Maybe the last comment on bug 48336 refers to this problem instead?

I can confirm that this is still exhibiting itself as of build 2001030110. Having had a further poke around, might this be a regression of bug 17158?

Sorry! I should think before typing in future. The "no proxy for" setting obviously works, but is not being used by the Java plugin. My apologies.

Marking worksforme. See attached testcase.

I'm using an authenticating proxy, so I'm unable to use the testcase due to bug 62218.

This is being taken care of in bug 69466. You are correct, it is a problem.

I'm fixing this problem under the aegis of bug 69466. *** This bug has been marked as a duplicate of 69466 ***

Verified.