The Java HTTP Client application was designed to be an HTTP client that comes built into Java.

Could it be:
· you need pipelining for high performance applications?
· you need a single sign-on authentication that supports NTLMv2?
· you need HTTP NTLM (including V2) client authentication support to communicate with Windows Servers (possibly for Apache Axis, Apache Axis2, SOAP or XML-RPC)?
· you are experiencing dropped connections and lost messages?
· you need to use WebDAV methods?
· you have trouble with connections being closed by the server?
· you need timeouts for connection establishment and request responses?
· you need tracing to see what's going on?
· you need better performance in handling long messages?
· you have run into other bugs in the HTTP client that Sun has not fixed?
· you have different behavior in the different HTTP clients by the application server vendors?

Its no wonder that some of the major application server vendors have their own HTTP client (IBM, BEA). But they still have problems, and none of them support NTLM client authentication.

Requirements:

· Requires JRE 1.4.2 or higher

Limitations:

· 30 days trial

What's New in This Release: [ read full changelog ]

· 977 Implement SOCKS 4/5 proxy support
· 2141 Handling bad response codes in raw streaming mode
· 2161 Use of Axis 1.4 also requires Axis2 libraries
· 2163 Reentering HTTP client on static initialization causes NPE
· 2175 Don't show passwords in logging output
· 2179 Don't start SSL unless it's needed
· 2180 Allow socket to creation to be specifed by user
· 2181 NTLM connections should be closed if they cannot be authenticated
· 2185 Support caching [proxy] connection credentials by host/port
· 2189 Allow JRE Compatible FileNotFoundException on 404 Response