HttpClient 4.1.3 is a bug fix release that addresses a number of non-critical issues found since 4.1.2 primarily in the HTTP caching module.
This is the first BETA release of HttpCore 4.2. This release ships with an improved asynchronous protocol handling API and new non-blocking client and server HTTP protocol handler implementations. New API is expected to be more flexible especially for writing HTTP proxy or gateway type of services. Upstream projects are encouraged to evaluate the new API and give feedback.
HttpCore 4.1.4 is a patch release that fixes a number of bugs found since 4.1.3. It is also likely to be the last release in the 4.1.x branch.
This is the first ALPHA release of HttpClient 4.2. The 4.2 branch enhances HttpClient in several key areas and includes several notable features and improvements:
This is the third ALPHA release of HttpAsyncClient 4.0. This release which largely completes the application programming interface and feature set of HttpAsyncClient. While the API may still change in the course of the ALPHA development phase, this is expected to be the last round of major API changes and the API is expected to be reasonably stable as of this release.
This is the second ALPHA release of HttpCore 4.2. This release comes with completely redesigned and rewritten asynchronous protocol handlers. New protocol handling API used in conjunction with connection pooling components introduced in the previous ALPHA release is expected to make development of asynchronous HTTP client agents and HTTP proxies easier and less error prone.
This is the first ALPHA release of the 4.2 development branch. The most notable feature included in this release is support for connection pools of blocking and non-blocking HTTP connections. Connection pool components are based on mature code migrated from HttpClient and HttpAsyncClient modules but have a slightly different API that makes a better use of Java standard concurrent primitives. Support for connection pools in HttpCore is expected to make development of client and proxy HTTP services easier and less error prone.
HttpClient 4.1.2 is a bug fix release that addresses a number of non-critical issues reported since release 4.1.1.
HttpCore 4.1.3 is a patch release that fixes a critical regression in the non-blocking SSL I/O session code introduced in the 4.1.2 release.
HttpCore 4.1.2 is a patch release that fixes a number of non-critical issues found since release 4.1.1.
The second ALPHA release of HttpAsyncClient 4.0 comes with a number of important improvements and enhancements. As of this version HttpAsyncClient fully supports HTTP state management (cookies) and HTTP authentication (basic, digest, NTLM, spnego/kerberos). Connection management classes have been thoroughly reworked and improved. This version also improves support for zero copy file upload / download operations.
HttpCore 4.1.1 is a patch release that fixes a number of non-critical issues found since release 4.1.
This release marks the end of support for Java 1.3. As of release 4.2 HttpCore will require Java 1.5 for all its components.
HttpClient 4.1.1 is a bug fix release that addresses a number of issues reported since release 4.1, including one critical security issue.
The HttpClient 4.1 release builds upon the stable foundation laid by HttpClient 4.0 and adds several functional improvements and popular features.
This is the first public release of HttpAsyncClient. The HttpAsyncClient 4.0 API is considered very experimental and is expected to change in the course of the ALPHA development phase. This release is primarily intended for early adopters who may be interested in contributing to the project and in helping shape the new API.
This release finalizes the 4.1 API and brings a number of major improvements to the HTTP caching module. This release also adds full support for NTLMv1, NTLMv2, and NTLM2 Session authentication schemes. The NTLM protocol code was kindly contributed by the Lucene Connector Framework project.
This is the first stable release of HttpCore 4.1. This release provides a compatibility mode with JREs that have a naive (broken) implementation of SelectionKey API and also improves compatibility with the Google Android platform. There has also been a number of performance related improvements and bug fixes in both blocking and non-blocking components.
This is an emergency release fixing a critical regression in the SSL connection management code.
This is a maintenance release that fixes a number of bugs found since 4.0.1. This is likely to be the last release in the 4.0.x branch.
This release addresses fixes a number of non-critical bugs. It is likely to be the last BETA release in the 4.1 branch.
This release fixes a number of non-severe bugs discovered since the last release and introduces support for two frequently requested features:
This release finalizes the API introduced in the 4.1 development branch. It also fixes a number of bugs discovered since the previous release and delivers a number of performance optimizations in the blocking HTTP transport components. The blocking HTTP transport is expected to be 5% to 10% faster compared to previous releases.
This release builds on the stable 4.0 release and adds several functionality improvements and new features.
This is a bug fix release that addresses a number of issues discovered since the previous stable release. None of the fixed bugs is considered critical. Most notably this release eliminates dependency on JCIP annotations.
This release is also expected to improve performance by 5 to 10% due to elimination of unnecessary Log object lookups by short-lived components.
This is the first public release from the 4.1 branch of HttpCore. This release adds a number of new features, most notable being introduction of compatibility mode with IBM JREs and other JREs with naive (broken) implementation of SelectionKey API.
This the first stable (GA) release in the 4.x code line. This release completes the rewrite of HttpClient and delivers a complete API documentation and fixes a few minor bugs reported since the previous release.
This is a patch release addressing a number of issues discovered since the 4.0 release.
This the first stable (GA) release in the 4.x code line. This release delivers complete API documentation and fixes a few minor bugs reported since the previous release.
The second BETA of HttpComponents HttpClient addresses a number of issues discovered since the previous release.
The only significant new feature is an addition of an OSGi compliant bundle combining HttpClient and HttpMime jars.
All upstream projects are strongly encouraged to upgrade.
The third BETA version of HttpComponents Core addresses a number of issues discovered since the previous release.
The only significant new feature is an addition of an OSGi compliant bundle combining HttpCore and HttpCore NIO jars.
HttpClient is among the 60 winners of InfoWorlds "Best of Open Source Software Awards 2008".
HttpClient was selected as one of the best open source development tools.
The first BETA brings yet another round of API enhancements and improvements in the area of connection management. Among the most notable ones is the capability to handle stateful connections such as persistent NTLM connections and private key authenticated SSL connections.
This is the first API stable release of HttpClient 4.0. All further releases in the 4.0 code line will maintain API compatibility with this release.
The second BETA version of HttpComponents Core added a number of improvements to the NIO components, most notable being improved asynchronous client side and server side protocol handlers.
The fourth ALPHA marks the completion of the overhaul of the connection management code in HttpClient. All known shortcomings of the old HttpClient 3.x connection management API have been addressed.
By 6 binding votes in favor and none against Sam Berlin has been voted in as a new HttpComponents committer. Sam made several valuable contributions to both core and client components in the course of the past several months.
Welcome on board, Sam!
The third ALPHA release brings another round of API refinements and improvements in functionality. As of this release HttpClient requires Java 5 compatible runtime environment and takes full advantage of generics and new concurrency primitives.
This release also introduces new default cookie policy that selects a cookie specification depending on the format of cookies sent by the target host. It is no longer necessary to know beforehand what kind of HTTP cookie support the target host provides. HttpClient is now able to pick up either a lenient or a strict cookie policy depending on the compliance level of the target host.
Another notable improvement is a completely reworked support for multipart entities based on Apache mime4j library.
The first BETA version of HttpComponents Core has been released. This release can be considered a major milestone, as it marks the end of API instability in HttpCore. As of this release the API compatibility between minor releases in 4.x codeline will be maintained.
This release includes several major improvements such as enhanced HTTP message parsing API and optimized parser implementations, Java 5.0 compatibility for HttpCore NIO extensions.
The focus of the development efforts will be gradually shifting towards providing better test coverage, documentation and performance optimizations.
The ASF board had approved HttpComponents 'graduation' from Jakarta to a TLP of its own.
We are now Apache HttpComponents Project!
The second ALPHA release is another important milestone in the redesign of HttpClient. The release includes a number of improvements since ALPHA1, among which are improved connection pooling, support for proxy chains, redesigned HTTP state and authentication credentials management API, improved RFC 2965 cookie specification.
The sixth ALPHA version of HttpComponents Core has been released. This release sports an improved message parsing and formatting API in the base module and lots of incremental improvements and bug fixes in the NIO and NIOSSL modules. Based on the improved API, it is now possible to send and receive SIP messages with HttpComponents Core.
This release represents a complete, ground-up redesign and almost a complete rewrite of the old HttpClient 3.x codeline. This release finally addresses several design flaws that existed since the 1.0 release and could not be fixed without a major code overhaul and breaking API compatibility.
Notable changes and enhancements:
The fifth ALPHA version of HttpComponents Core has been released. This release delivers a number of incremental improvements across the board in all modules and adds several performance oriented features such as ability to transfer data directly between a file and a socket NIO channels.
The fourth ALPHA version fixes a number of bugs and adds a number of improvements to HttpCore base and the HttpCore NIO extensions. This release also introduces NIOSSL extensions that can be used to extend HttpCore non-blocking transport components with the ability to transparently encrypt data in transit using SSL/TLS.
The third ALPHA version of HttpCore has been released. The ALPHA3 release includes a number of API optimizations and improvements and introduces a set of NIO extensions to the HttpCore API. NIO extensions can be used to build HTTP services intended to handle thousands of simultaneous connections with a small number of I/O threads.
The second ALPHA version of HttpCore has been released, which addresses a number of non-critical problems found in the previous release. The upstream projects are strongly encouraged use this release as a dependency while HttpCore undergoes another round of reviews and optimization in the SVN trunk.
HttpClient issue tracking has migrated from Bugzilla to Jira. Please use this project in Jira to report new issues against HttpClient and search for reported ones. All existing issue reports can be accessed in Jira by their original Bugzilla bug id.
HttpComponents project now has a brand new logo kindly contributed by Regula Wernli.
Many thanks, Regula!
This is the first ALPHA release of HttpCore intended for API review and use in experimental projects. The HttpCore API is still deemed unstable and it can still undergo significant changes based on the feedback from early adopters.
By 5 binding votes in favor and none against Roland Weber has been voted in as a new HttpComponents committer. Roland has been an invaluable contributor to the Jakarta Commons HttpClient project for many years and he is the very first committer to join the Jakarta HttpComponents project.
Welcome, Roland