tree 3bfcd616b6604c8b2ff2871fd2d0c74007e91528
parent 06c75fec1783f1641b11f627be06f7df26e9d282
author Willy Tarreau <w@1wt.eu> 1503473526 +0200
committer Willy Tarreau <w@1wt.eu> 1503497498 +0200
encoding latin1

MINOR: lua: properly process the contents of the content-length field

The header's value was parsed with atoi() then compared against -1,
meaning that all the unparsable stuff returning zero was not considered
and that all multiples of 2^32 + 0xFFFFFFFF would continue to emit a
chunk.

Now instead we parse the value using a long long, only accept positive
values and consider all unparsable values as incorrect and switch to
either close or chunked encoding. This is more in line with what a
client (including haproxy's parser) would expect.

This may be backported as a cleanup to stable versions, though it's
really unlikely that Lua applications are facing side effects of this.