[NIFI-1396] PostHttp will always use Chunked Encoding

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 0.5.0
• Assignee: Joe Percivall
• Reporter: Joe Percivall
• Created: 15/Jan/16 03:20
• Updated: 28/Jan/16 19:51
• Resolved: 28/Jan/16 19:51

Description

The PostHttp processor has a boolean property for whether to set the chunked flag (header "Transfer-Encoding"). Even if the property is set to false the content will always be chunked because the content is streamed and the content length is not known. Comment on setting the chunked flag:

Note that the chunked setting is a hint only.

• If using HTTP/1.0, chunking is never performed.
• Otherwise, even if chunked is false, HttpClient must
• use chunk coding if the entity content length is
• unknown (-1).

The processor needs to properly enable the chunking option which will require determining the length of the content.

Issue Links

• duplicates: NIFI-21 PostHTTP does not always honor chunked encoding setting