Version: 3.1.2 (using KDE KDE 3.1.2) Installed from: SuSE RPMs Compiler: gcc-3.3 OS: Linux I've got an applet I'm trying to load from an internal webserver, let's call him webdev1. The hostname is mapped to an IP specified in my /etc/hosts file since I need a hostname for the webserver to resolve. - If I load the page containing the applets w/o any proxy specified, it loads fine - If I load the page with a proxy specified and use the IP address instead of the hostname (i.e. http://192.168.1.2), it works fine - If I load the page with a proxy specified but use the hostname instead (i.e. http://webdev1), I get loads of ClassNotFoundExceptions and the applet can't load - If I load a page with an applet somewhere on the Internet (i.e. Sun's site), their applet works fine proxied. Bear in mind that Konqueror is using an autoconfig script to determine what to proxy and what to connect to directly. Here's the wpad.dat: function FindProxyForURL(url, host) { if(isPlainHostName(host)) { return "DIRECT"; } else { return "PROXY 192.168.1.1:3128; DIRECT"; } } So the problem is that all sites that meet the DIRECT response fail and are improperly loaded. Konqueror is unique in this problem since it loads the actual JRE externally instead of using a plugin. This means that Mozilla, IE, etc. do not exibit this problem - I'm guessing since they rely in their own internal implementations for applet classloaders. This would seem to indicate that either the JRE or Konqueror is improperly trying to load Java classes from the wrong source (maybe requesting it from the proxy, not realizing that the connection was made DIRECT). I've tried this with Blackdown 1.3.1, Blackdown 1.4.1 and Sun's 1.4.1_02 so it's not distro-specific. Oh yeah - setting the autoconfig script in the ControlPanel app doesn't help either.
I suspect that konqueror _always_ uses the proxy in this case. I guess this will then fail because the proxy doesn't know webdev1.
That's what seems to be the case, given the TCP dumps I'm looking at and the stack trace from the Java console. Mozilla & IE seem to set proxy I/O at the plugin level (instead of with the JRE); but maybe KJAS could mimic the same actions that the Sun's ControlPanel application (in Blackdown it's JavaControlPanel or something) performs. It can be fed parameters to utilize an autoconfig script or static settings - that way proxy configs can be done directly on JRE level.
*** Bug 70933 has been marked as a duplicate of this bug. ***
Closing this one, because proxy problems are solves by using the 'Use KIO' option. The is no need anymore to build an infrastructure for proxing settings for the not-using-kio-case