From: Dridi Boukelmoune <dridi.boukelmoune@gmail.com>
Date: Wed, 30 Mar 2022 05:58:23 +0000 (+0200)
Subject: IMPORT: slz: mention the potential header in slz_finish()
X-Git-Tag: v2.7-dev9~103
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=4bd53c397c67535bbf1bc67dcc60b49a1c5c3912;p=thirdparty%2Fhaproxy.git

IMPORT: slz: mention the potential header in slz_finish()

There may be 2 or 10 bytes sent respectively for zlib and gzip.

This is libslz upstream commit de1cac155ac730ba0491a6c866a510760c01fa9b
---

diff --git a/include/import/slz.h b/include/import/slz.h
index d7d4863509..d01599ca44 100644
--- a/include/import/slz.h
+++ b/include/import/slz.h
@@ -152,7 +152,9 @@ static inline long slz_encode(struct slz_stream *strm, void *out,
  * possibly pending bits from the queue (up to 24 bits), rounding to the next
  * byte, then 4 bytes for the CRC when doing zlib/gzip, then another 4 bytes
  * for the input length for gzip. That may about to 4+4+4 = 12 bytes, that the
- * caller must ensure are available before calling the function.
+ * caller must ensure are available before calling the function. Note that if
+ * the initial header was never sent, it will be sent first as well (up to 10
+ * extra bytes).
  */
 static inline int slz_finish(struct slz_stream *strm, void *buf)
 {