The Apache Software Foundation
The Apache HttpComponents project is pleased to announce the release of
HttpComponents HttpCore 4.1.3 (GA).
This release fixes a critical regression introduced in version 4.1.2.
Under special circumstances non-blocking SSL sessions may fail to
terminate correctly if the opposite end shuts down connection without
sending a 'close notify' message causing an infinite loop in the I/O
dispatch thread.
All users of HttpCore NIO are strongly advised to upgrade.
Download -
<http://hc.apache.org/downloads.cgi >
Release notes -
<http://www.apache.org/dist/httpcomponents/httpcore/RELEASE_NOTES-4.1.x.txt >
HttpComponents site -
<http://hc.apache.org/>
About HttpComponents Core -
HttpCore is a set of low level HTTP transport components that can be
used to build custom client and server side HTTP services with a minimal
footprint. HttpCore supports two I/O models: a blocking I/O model based
on the classic Java I/O and a non-blocking, event driven I/O model based
on Java NIO. The blocking I/O model may be more appropriate for data
intensive, low latency scenarios, whereas the non-blocking model may be
more appropriate for high latency scenarios where raw data throughput is
less important than the ability to handle thousands of simultaneous HTTP
connections in a resource efficient manner.
HttpComponents HttpCore 4.1.3 (GA).
This release fixes a critical regression introduced in version 4.1.2.
Under special circumstances non-blocking SSL sessions may fail to
terminate correctly if the opposite end shuts down connection without
sending a 'close notify' message causing an infinite loop in the I/O
dispatch thread.
All users of HttpCore NIO are strongly advised to upgrade.
Download -
<http://hc.apache.org/
Release notes -
<http://www.apache.org/dist/
HttpComponents site -
<http://hc.apache.org/>
About HttpComponents Core -
HttpCore is a set of low level HTTP transport components that can be
used to build custom client and server side HTTP services with a minimal
footprint. HttpCore supports two I/O models: a blocking I/O model based
on the classic Java I/O and a non-blocking, event driven I/O model based
on Java NIO. The blocking I/O model may be more appropriate for data
intensive, low latency scenarios, whereas the non-blocking model may be
more appropriate for high latency scenarios where raw data throughput is
less important than the ability to handle thousands of simultaneous HTTP
connections in a resource efficient manner.