tree 7a0e0883d00eaaf5fe4cb203d873b6c10fc75c13
parent 1030597d8b2227c9dae91fb7ffdd840b7816a8b3
author Christopher Faulet <cfaulet@haproxy.com> 1578314461 +0100
committer Christopher Faulet <cfaulet@haproxy.com> 1578590066 +0100

BUG/MINOR: h1: Report the right error position when a header value is invalid

During H1 messages parsing, when the parser has finished to parse a full header
line, some tests are performed on its value, depending on its name, to be sure
it is valid. The content-length is checked and converted in integer and the host
header is also checked. If an error occurred during this step, the error
position must point on the header value. But from the parser point of view, we
are already on the start of the next header. Thus the effective reported
position in the error capture is the beginning of the unparsed header line. It
is a bit confusing when we try to figure out why a message is rejected.

Now, the parser state is updated to point on the invalid value. This way, the
error position really points on the right position.

This patch must be backported as far as 1.9.

(cherry picked from commit 1703478e2dd6bd12bb03b0a0fdcc7cd4a611dafc)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
(cherry picked from commit e313c1bd5901b721bdfd23714c432235625a87a8)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>