Version: 3.4.3 (using KDE 3.4.3, Gentoo) Compiler: gcc version 3.3.6 (Gentoo 3.3.6, ssp-3.3.6-1.0, pie-8.7.8) OS: Linux (i686) release 2.6.11.11 This might be related to bug #59961. I set up privoxy and tor as described here [1]. The proxy settings in konqueror are enabled and work. Now, when accessing a website with java applications (e.g. a webchat), java happily accesses the server directly -- ignoring the proxy settings completely. $> lsof -i | grep $externalhost$ java 21998 $user$ 6u IPv4 3233900 TCP $localhost$:32834->$externalhost$:3004 (ESTABLISHED) [many more lines] $externalhost$ also reports my correct ip, instead of any ip from the tor network. My Java settings look like this: Path to Java executable: /opt/blackdown-jre-1.4.2.02/bin/java Additional java arguments: -DproxySet=true -DproxyPort=8118 -DproxyHost=localhost [2] Bug #59961 suggests to enable KIO, but the results are the same, whether "Use KIO" is enabled or not. At startup, the Java konsole displays: "proxy: 127.0.0.1:null" The host is correct, the port obviously isn't?! [1] http://gentoo-wiki.com/HOWTO_Anonymity_with_Tor_and_Privoxy [2] http://www.davidreilly.com/java/java_network_programming/#2.4
Here's some output from java kosole (edited, removed some lines): Java VM: Blackdown Java-Linux Team 1.4.2-02 Proxy: 127.0.0.1:null SecurityManager=org.kde.kjas.server.KJASSecurityManager@12940b3 ---------------------------------------------------- Printing System Properties ... ---------------------------------------------------- java.runtime.name = Java(TM) 2 Runtime Environment, Standard Edition java.vm.version = Blackdown-1.4.2-02 java.vm.vendor = Blackdown Java-Linux Team [...] proxySet = true proxyPort = 8118 proxyHost = localhost http.proxyPort = 8118 http.proxyHost = 127.0.0.1 java.security.manager = org.kde.kjas.server.KJASSecurityManager kjas.useKio = kjas.showConsole = ---------------------------------------------------- When dumping this info, "Use KIO" and "Show Java console" were set in Konqueror -> Configure -> Java & JavaScript
Message from the Bugsquad and Konqueror teams: This bug is closed as outdated, as we do not have the manpower to maintain the KDE3 version anymore. If you still can reproduce this issue with Konqueror 4.8.4 or later, please open a new report. Thank you for your understanding.