Release Notes: This release fixes a possible crash introduced in 1.3.17 when built on x86_64 with HTTP logging enabled. It fixes an issue where the old process sometimes remained present after a soft reload. All stats counters have been switched to 64-bit. There is a new header hash balancing algorithm. It is now possible to log invalid requests/responses without blocking them. Many warnings were added for possibly erroneous configurations. The documentation has been greatly improved. The RPM spec files have been fixed and cleaned up for easier builds.
Release Notes: This version fixes a few timeout handling issues introduced in 1.3.16 causing haproxy to quickly rise to 100% CPU usage in some environments. With this version, 1.3 becomes the new stable version, providing many new features including conditional redirection, kernel-based TCP splicing, session rate limiting, TCP content filtering, invalid request/response captures, binding to specific interfaces, and many others. Users of 1.3.16 are encouraged to quickly upgrade.
Release Notes: This release brings new long-awaited features, among which are TCP splicing support, conditional redirection, TCP content filtering, session rate reporting and limiting, invalid request/response capture, binding to specific network interfaces, per-process affinity for frontends and backends, a monotonic internal clock, and many others. The internal architecture has been reworked in layers to ease development, enhance reliability, and improve performance. Performance gains of about 10% are to be expected compared to 1.3.15.
Release Notes: Several minor bugs were fixed, mainly configuration parsing oddities. Another bug affected the way servers may track each other. People using the "track" keyword are encouraged to upgrade. The documentation has been largely updated, covering the log format.
Release Notes: Since 184.108.40.206, problems were fixed with hot-restart where the old process would not always stop, cookie capture was fixed (as it was broken since the frontend/backend split), critical startup errors are now reported on the console, and a failing server will no longer consume pending requests from the global queue. This last problem was the cause of many 503 errors for some people.
Release Notes: The connections regulation mechanism could send more connections than the allowed limit to a server when this server had just rejected a connection attempt; for servers with very low connection limits such as mongrel, this could easily trigger timeouts. The slowstart mechanism could return a limit of zero connections for very low maxconn values, causing servers to re-enter the farm a bit late.
Release Notes: Several timeouts were not correctly updated on some rare occasions. A possible segfault when using "url_param check_post" has been fixed. regparm is disabled on gcc versions < 3. "use_backend" would not correctly consider "unless". This last change should probably be the real reason to upgrade, as check_post is rarely used.
Release Notes: The queue/dequeue logic was reworked; using a low server maxconn value to serialize requests could result in some requests never being served. Users are encouraged to upgrade, especially those running haproxy in front of mongrel. All versions are affected. Version 220.127.116.11 was also released to address this problem in the previous branch.
Release Notes: Building with gcc 4.3 has been fixed. A condition where statistics could be truncated if exactly zero bytes remained in the buffer has been fixed. An event starvation that caused connection acceptance to slow down when approaching 40000 concurrent connections at gigabit speed has been fixed.
Release Notes: This release fixes building of rbtree on BSD, and fixes an early server close after a client close. These are long-standing fixes that were available but not in any released version.