I am not sure where the fault lies, in Java's interpretation of this, or in Firefox not clearing this field. In either browser, if the SOCKS proxy is turned on and filled out, webstart will fail with this test. In IE, checking the analogous box actually *clears* the SOCKS check box. In FireFox, setting the proxy once and then checking the "Use this proxy server for all protocols" sets the SOCKS proxy and causes this test case to fail. Looking a bit deeper into browser behavior: This may explain why HttpURLConnection does not get the error as socket created using the. Protected Socket doConnect (String server, int port) which creates sockets via new Socket(.).
This does not use the socket factories, but uses: Upon investigation, it looks like HttpURLConnection eventually gets its sockets from. Strangely, this does not cause a problem when using HttpURLConnection. Using the default mechanisms in apache's HttpClient, I get the error: "Reply from SOCKS server has bad version". Hardware Configuration Information (be specific): Operating System Configuration Information (be specific): Not really! It can happen but probably won't in realistic scenarios. Java HotSpot(TM) Client VM (build 1.6.0_01-ea-b02, mixed mode, sharing)ĭoes this problem occur on J2SE 1.4.x or 5.0.x ? Yes / No (pick one) Java(TM) SE Runtime Environment (build 1.6.0_01-ea-b02) J2SE Version (please include all output from java -version flag):
0 kommentar(er)
