Release Notes: All fixes from version 1.4.9 were merged. Stickiness tables can now be synchronized between multiple active haproxy nodes. Sticky information is also learned from responses, providing support for SSL-ID. Connections can be accepted over Unix sockets. A new PROXY protocol was implemented to let other components (such as stunnel) pass connection information to haproxy.
Release Notes: Some minor bugs were fixed and several usability improvements were made. The Web interface now allows you to enable or disable servers. The ECV and LDAPv3 checks were merged. The MySQL check was improved to support a real login sequence. Persistence cookies can now be timestamped to support a maximum idle time and a maximum life time, and can be removed by the server if needed (e.g. logout). The SNMP plugin was improved to report socket stats, and some Cacti templates were merged. The halog tool can now instantly report per-URL response times.
Release Notes: Support was introduced for per-IP accounting and filtering based on connection counts, rates, byte counts, rates, error counts and rates, and a few other criteria. It is now possible to filter very early at the connection level based on these critieria, resulting in a measured protection capacity of more than 200000 connections per second. This is the first development version of branch 1.5, which should be released around the end of the year. This version is in sync with all the fixes that are available in 1.4.8, and appears reliable enough to be used in production if needed.
Release Notes: A bug introduced in 1.3.16 which can cause crashes when using monitor-net in TCP only frontends has been fixed. The appsession cookie name check is now correctly performed on the whole name length. The forceclose option is now ignored for TCP instances because it can cause unexpected timeouts. Connection rate limiting was using more CPU than required and was fixed too. Upgrading is recommended for users of 1.3 with TCP frontends.
Release Notes: The recent memleak fix in 1.4.7 broke the stick tables. A major bug was present since 1.3.16, which can cause crashes when using monitor-net on TCP-only frontends due to a reference not being released. Both issues have been fixed. Some unclear parts of the documentation were updated. Upgrading is recommended if stick-tables are used.
Release Notes: This release fixed problems where consistent hashing was broken when no server ID was specified in the configuration and some errors were incorrectly reported as failed instead of denied in the statistics. The dispatch and http_proxy modes were fixed. A few termination flags in the logs used for troubleshooting were corrected. A few other minor issues were fixed. Upgrading is recommended.
Release Notes: A build issue on Linux distributions with glibc >= 2.10 was fixed. A minor precision about RDP cookies was added to the documentation, and a new ACL keyword was added. Those who had no problem building and running 1.4.5 don't need to upgrade.
Release Notes: Haproxy can now read huge ACL pattern lists from files and match inputs against them without any noticeable performance impact, making geolocation possible. It also adds a new "ignore-persist" directive, allowing it to ignore the persistence cookie if an ACL-based condition is matched (which is useful for static objects in stateful farms). There were a few other minor improvements and a nice performance boost of the log analyzer, which can now process more than 1 GB of logs per second and report request counts by status codes.
Release Notes: This version brings a new option to work around optimization issues with Tomcat and Jetty in server close mode, and for a bug in Jetty's handling of Expect: 100-continue. A very old appsession unexpected match of shorter cookie names was also fixed. A new feature to make it possible to connect to a server from an IP found in a header was merged. It allows you to run stunnel+haproxy in transparent mode together.
Release Notes: This release fixes a regression introduced in 1.4.2 which could cause a connection to still be attempted on the server side in case of an error on the client side. This issue could even lead to a crash if a Layer7 hash algorithm was used, so this code was strengthened. The configuration parser now detects many more inappropriate options in TCP mode and emits related warnings. It is now possible to indicate in the configuration that a server will start in the "disabled" state. Other very minor issues were fixed.