In the mess, and under pressure, I learned something quite important about Jakarta Commons HTTPClient: it doesn't use the system's proxy settings. Why? Because this is platform-dependant.
Let me be more precise: depending on what implementation of Java you use and what version, you may or may not have the proxy settings from the OS. On some implementations, the settings will be placed in System.getProperty("http.proxyHost"), http.proxyPort, https.proxyHost and https.proxyPort. On others (for example JRE 1.5.0_04 implemented by Sun for Windows 2000/XP), you'll only have javaplugin.proxy.config.list, whose value is in the form "http=host:port,https=host:port" (or "http=host:port," or ",https=host:port").
Follow this example to see how much this is a total mess...
That's not the kind of stuff you'd like to learn under pressure while the client, behind a stupid corporate firewall and a stupid proxy, cannot connect to the server using your client...
Published on September 29, 2005 at 18:42 EDT
Older post: Practical Distributed Version Control
Newer post: Manage your life with Subversion