[
https://issues.apache.org/jira/browse/NIFI-1396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Percivall updated NIFI-1396:
-----------------------------------
Attachment: 0001-NIFI-1396-Correcting-PostHttp-chunked-encoding-funct.patch
Added the proper functionality and corrected the property descriptor to reflect
when it's used.
The chunked encoding property is ignored when using compression or sending as
flowfiles. It is ignored when compressing because a GZIPOutputStream is being
used and the content-length won't be known ahead of time. It is ignored while
processing flowfiles because it is using a different protocol (Site to site).
> PostHttp will always use Chunked Encoding
> -----------------------------------------
>
> Key: NIFI-1396
> URL: https://issues.apache.org/jira/browse/NIFI-1396
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Joseph Percivall
> Assignee: Joseph Percivall
> Priority: Minor
> Fix For: 0.5.0
>
> Attachments:
> 0001-NIFI-1396-Correcting-PostHttp-chunked-encoding-funct.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
