BUG/MINOR: h3: always reject PUSH_PROMISE
The condition for checking PUSH_PROMISE was not correctly interpreted
from the RFC. Initially, it rejects such a frame for every stream
initiated from client side.
In fact, the RFC indicates that PUSH_PROMISE are never sent by a client.
Thus, it can be rejected in any case until HTTP/3 will be implemented on
the backend side.
This should be backported up to 2.6.
(cherry picked from commit 74ba22b1eeaeb96b74d3a4f7abdead88e9b4f413)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
1 file changed