HAProxy known bugs for maintenance branch 3.2 : 5

This is maintenance branch 3.2 whose latest version is 3.2.1. If your version is not the last one in the maintenance branch, you are missing fixes for known bugs, and by not updating you are needlessly taking the responsibility for the risk of unexpected service outages and exposing your web site to possible security issues.

The HAProxy development team takes a great care of maintaining stable versions so that all users can apply bug fixes without having to take the risk of upgrading to a new branch. In turn users are expected to apply the fixes when the development team estimates that they were worth being backported to stable branches. In short, if you are running any 3.2 version other than 3.2.1, you're running with known bugs.

Quick links

full changelog for 3.2 : here
browse history for 3.2 : here

Versions available in this branch

This branch contains the following releases :

Date Version Comment

2025-06-11 3.2.1 ⇐ last

2025-05-28 3.2.0

Date	Version	Comment
2025-06-11	3.2.1	⇐ last
2025-05-28	3.2.0

Fixes for known bugs pending in this branch since the last release (3.2.1)

These fixes have already been queued for the next 3.2 release but no version was released with them yet. Note that fixes are backported several at a time from the development branch to maintenance branches, and the absence of a fix here doesn't mean none will be issued soon.

Bugs are almost always tagged with a severity (some people forget the severity tag when the bug is minor). The following severities are used :

MINOR: the bug presents a limited impact and can easily be mitigated ; users rarely upgrade just for these ones ;
MEDIUM: the bug can cause some undesired behaviour and may require some tricky configuration changes to avoid hitting it ; users normally upgrade to get rid of them, or temporarily disable a functionality.
MAJOR: the bug affects short term reliability and cannot easily be worked around without a significant performance penalty or without a significant functional loss ; such bugs don't stay long in the queue without a release and users must plan an upgrade as soon as possible ;
CRITICAL: this one very rarely happens ; it indicates a short-term reliability or security issue for which there is no workaround. A release will be emitted for this fix even if it's alone and users are urged to upgrade immediately. Some distro maintainers might have been informed in advance in order to agree on a coordinated release date.

Total known bugs in the latest version of this branch by category :

Total CRITICAL MAJOR MEDIUM MINOR

5 0 0 2 3

Total	CRITICAL	MAJOR	MEDIUM	MINOR
5	0	0	2	3

Click on the subjects below to get the full description of the bug :

Merge date Subject - Severity (minor, medium, major, critical)

2025-06-16 BUG/MEDIUM: check: Set SOCKERR by default when a connection error is reported

2025-06-16 BUG/MEDIUM: cli: Don't consume data if outbuf is full or not available

2025-06-16 BUG/MINOR: quic: Fix OSSL_FUNC_SSL_QUIC_TLS_got_transport_params_fn callback (OpenSSL3.5)

2025-06-13 BUG/MINOR: http-ana: Properly handle keep-query redirect option if no QS

2025-06-13 BUG/MINOR: config/server: reject QUIC addresses

Merge date	Subject - Severity (minor, medium, major, critical)
2025-06-16	BUG/MEDIUM: check: Set SOCKERR by default when a connection error is reported
2025-06-16	BUG/MEDIUM: cli: Don't consume data if outbuf is full or not available
2025-06-16	BUG/MINOR: quic: Fix OSSL_FUNC_SSL_QUIC_TLS_got_transport_params_fn callback (OpenSSL3.5)
2025-06-13	BUG/MINOR: http-ana: Properly handle keep-query redirect option if no QS
2025-06-13	BUG/MINOR: config/server: reject QUIC addresses

Known bugs fixed in the development branch after the last commit in this branch

It is important to understand that not all of these commits are necessarily relevant to this version, but clicking on them will show the bug description. All fixes are made first in the development branch and then backported to the maintenance branches. This ensures no fix is lost when upgrading. If a fix was marked for backporting to this branch and is not there yet, it's likely that it is still missing. Do not hesitate to ask on the haproxy mailing list if you feel like a fix has been skipped.

Date Subject

2025-06-20 BUG/MEDIUM: quic: do not release BE quic-conn prior to upper conn

2025-06-20 BUG/MAJOR: fwlc: Count an avoided server as unusable.

2025-06-18 BUG/MINOR: mux-quic/h3: properly handle too low peer fctl initial stream

2025-06-17 MINOR: h3: use BUG_ON() on missing request start-line

2025-06-16 BUG/MINOR: mux-quic: check sc_attach_mux return value

2025-06-16 BUG/MEDIUM: check: Set SOCKERR by default when a connection error is reported

2025-06-16 BUG/MEDIUM: cli: Don't consume data if outbuf is full or not available

2025-06-16 BUG/MINOR: quic: fix ODCID initialization on frontend side

2025-06-16 BUG/MINOR: quic: Fix OSSL_FUNC_SSL_QUIC_TLS_got_transport_params_fn callback (OpenSSL3.5)

Date	Subject
2025-06-20	BUG/MEDIUM: quic: do not release BE quic-conn prior to upper conn
2025-06-20	BUG/MAJOR: fwlc: Count an avoided server as unusable.
2025-06-18	BUG/MINOR: mux-quic/h3: properly handle too low peer fctl initial stream
2025-06-17	MINOR: h3: use BUG_ON() on missing request start-line
2025-06-16	BUG/MINOR: mux-quic: check sc_attach_mux return value
2025-06-16	BUG/MEDIUM: check: Set SOCKERR by default when a connection error is reported
2025-06-16	BUG/MEDIUM: cli: Don't consume data if outbuf is full or not available
2025-06-16	BUG/MINOR: quic: fix ODCID initialization on frontend side
2025-06-16	BUG/MINOR: quic: Fix OSSL_FUNC_SSL_QUIC_TLS_got_transport_params_fn callback (OpenSSL3.5)

Back to the list of branches and versions
Back to the HAProxy page