DOC: config: clarify some known limitations of the json_query() converter
authorWilly Tarreau <w@1wt.eu>
Thu, 2 Oct 2025 02:52:33 +0000 (04:52 +0200)
committerChristopher Faulet <cfaulet@haproxy.com>
Thu, 2 Oct 2025 07:53:14 +0000 (09:53 +0200)
commit56948689cf1dd58222b57530a5628a35ad347cb3
tree55b096d3853b64dc15fb69c2b93817a18694b569
parent83805a611b1622c0664846e61549c9f35845f306
DOC: config: clarify some known limitations of the json_query() converter

Oula Kivalo reported that different JSON libraries may process duplicate
keys differently and that most JSON libraries usually decode the stream
before extracting keys, while the current mjson implementation decodes the
contents during extraction instead. Let's document this point so that
users are aware of the limitations and do not rely on the current behavior
and do not use it for what it's not made for (e.g. content sanitization).

This is also the case for jwt_header_query(), jwt_payload_query() and
jwt_verify(), which already refer to this converter for specificities.

(cherry picked from commit 67603162c1d5baaf17f6bf1a3a4c58d5c0524d35)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
(cherry picked from commit d808c48fb926813438f58dad2654bd9a6a923ce4)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
(cherry picked from commit e09bf0ff4e73819e32075fd37abefb746799f373)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
doc/configuration.txt