]> git.kaiwu.me - haproxy.git/commit
projects / haproxy.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: b9aa1c0) | patch
BUG/MEDIUM: h3: Properly handle PUSH_PROMISE on backend connections
authorOlivier Houchard <ohouchard@haproxy.com>
Fri, 12 Jun 2026 11:39:07 +0000 (13:39 +0200)
committerOlivier Houchard <cognet@ci0.org>
Fri, 12 Jun 2026 12:01:07 +0000 (14:01 +0200)
commit98b1fd4ff9a719f34131fa04cbd93f92c0c362f7
tree320f806c099a18f162d9ca0f773a6cbae9df38b2tree | snapshot
parentb9aa1c0e644a1a97f7b2ba780b8e17f841a225e4commit | diff
BUG/MEDIUM: h3: Properly handle PUSH_PROMISE on backend connections

When we receive a PUSH_PROMISE frame while we don't expect it, flag it
as a connection error, do not just set ret to H3_ERR_ID_ERROR, as it
would just be considered the number of bytes we read, and could lead to
random corruption. This should only happen with backend connections.
This should be backported whenever commit 4a8bb2fe5 is backported.
src/h3.c diff | blob | history
haproxy upstream