tree ed9a3e07e345d68440c97c920c7716ae37c76972
parent 5696f5450ee2f14ba962ef365569599be33df658
author Christopher Faulet <cfaulet@haproxy.com> 1606922002 +0100
committer Christopher Faulet <cfaulet@haproxy.com> 1611848234 +0100

MEDIUM: mux-h1: Don't emit any payload for bodyless responses

Some responses must not contain data. Reponses to HEAD requests and 204/304
xresponses. But there is no warranty that this will be really respected by
the senders or even if it is possible. For instance, the method may be
rewritten by an http-request rule (HEAD->GET). Thus, it is not really
possible to always strip the payload from the response at the receive
stage. And the response may be emitted by an applet or an internal service
not strictly following the spec. All that to say that we may be prepared to
handle payload for bodyless responses on the sending path.

So, thanks to previous patches, it is now possible to know on the sending
path if a response must be bodyless or not. So, for such responses, no
payload is emitted, all HTX blocks after the EOH are silently removed
(including the trailers).