Prefer chunked Transfer-Encoding over Content-Length

[kevinresol]

IncomingRequest.parse framed the request body by Content-Length whenever that header was present, even if a chunked Transfer-Encoding was also present. Per RFC 7230 §3.3.3, if a message has Transfer-Encoding: chunked the Content-Length must be ignored and the body decoded as chunked.

• When Content-Length is present, still decode the body as chunked if the Transfer-Encoding includes chunked.
• Match the chunked transfer-coding token case-insensitively (both in the Content-Length and no-length branches).

Added a TestHeader case asserting that a request with both Content-Length and Transfer-Encoding: Chunked decodes the chunked body.

Made with Cursor