{"id":116174,"date":"2024-05-30T00:20:35","date_gmt":"2024-05-29T22:20:35","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-http-tcp-balansirovshhika-haproxy-3-0"},"modified":"2024-05-30T00:20:35","modified_gmt":"2024-05-29T22:20:35","slug":"vypusk-http-tcp-balansirovshhika-haproxy-3-0","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-http-tcp-balansirovshhika-haproxy-3-0","title":{"rendered":"Release of the HAProxy 3.0 HTTP\/TCP Load Balancer","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Five years after the 2.0 branch was formed, the HAProxy 3.0 load balancer has been released, allowing for the distribution of HTTP traffic and arbitrary TCP requests among a group of servers, taking into account multiple factors (for example, checking server availability, assessing load levels, having DDoS mitigation measures) and performing initial data filtering (such as parsing HTTP headers, filtering out incorrect query parameters, blocking SQL injection and XSS, and integrating content processing agents). HAProxy can also be used to coordinate interactions between components in microservices-based architectures. The project code is written in C and is distributed under the GPLv2 license. The project is used on many major sites, including Airbnb, Alibaba, GitHub, Imgur, Instagram, Reddit, StackOverflow, Tumblr, Twitter, and Vimeo. <\/p>\n
The HAProxy 3.0 branch is classified as a long-term support (LTS) release and will be maintained until 2029. Key changes: <\/p>\n
\n
A new section «crt-store» has been added to the configuration for managing the storage and usage of TLS certificates. Unlike the previous crt-list setting, the crt-store separates the certificate storage from its usage in the frontend, allowing for individual specification of the storage location for each certificate component (files containing certificates, keys, and OCSP data).\n
The ability to set limits for requests using HTTP\/2, allowed by the protocol but potentially problematic, has been added. For example, sending a CONTINUATION frame stream may lead to a DoS attack known as Continuation flood.\n
A new configuration directive «guid» has been added, which can be used in the «frontend», «backend», and «listen» sections. This directive binds a unique identifier to these sections, allowing the associated statistics to be retained after a restart (the Stats page state will not be reset). To save statistics to a file, a new command «dump stats-file» has been introduced, and a new configuration directive «stats-file» has been added for reading from a file after a restart.\n
Enhanced capabilities for balancing Syslog messages. The ability to assign weight coefficients for server-related strings in backend logs has been introduced.\n
Support for logging string formatting in JSON and CBOR format has been added.\n
The data that can be retrieved using information extraction functions has been expanded, for example, it is now possible to request details about the number of open HTTP sessions for both backend and frontend, the size of the request processing queue, and the allowed number of simultaneous sessions.\n
The performance of single-threaded Lua scripts loaded via the «lua-load» directive has been enhanced.\n
The performance of in-memory storage areas created using the stick-table directive has significantly improved; for instance, in a system with 80 threads, performance increased by 6 times.\n