Le 16/10/2019 à 08:48, GARDAIS Ionel a écrit :
Hi Christopher,
First : good news : I was not able to reproduce the issue with
2.1-dev2-e0f48a-88 and HTX enable.
I guess e0f8dc576f62ace9ad1055ca068ab5d4f3a952aa was the culprit.
To answer your questions and for others on the list :
- The issue arose with H1 (H2 not enable)
- It's the client who complained about a malformed payload thus it was unable
to unmarshall datas into a valid object (it was the result of an API call).
The message from the client is a short error message like "expecting [0-9a-fA-F] but
got 0x4f" (note that 0x4f is not a constant and would vary from run to run)
- To my understanding, the payload is chunk-encoded.
Hi,
Thanks to confirm. So it is indeed a problem of chunking fixed by the commit
e0f8dc576. The patch was backported to 2.0 and 1.9.
Thanks for your help,
--
Christopher Faulet
