[
https://issues.apache.org/jira/browse/NIFI-10161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17617938#comment-17617938
]
David Handermann commented on NIFI-10161:
-----------------------------------------
[~relaynetwork] It would be helpful to comment on the new issue NIFI-10430 as
opposed to this closed issue. The project receives many bug reports and feature
requests, and unfortunately time does not permit resolving every issue in the
subsequent release. One workaround would be to use HandleHttpRequest and
HandleHttpResponse, but that would require Flow changes, so it is not ideal. I
will evaluate options and follow up with comments on NIFI-10430.
> Add Gzip Request Content-Encoding in InvokeHTTP and ListenHTTP
> --------------------------------------------------------------
>
> Key: NIFI-10161
> URL: https://issues.apache.org/jira/browse/NIFI-10161
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Minor
> Fix For: 1.17.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> [RFC 7231 Section
> 3.1.2.2|https://datatracker.ietf.org/doc/html/rfc7231#section-3.1.2.2]
> describes the {{Content-Encoding}} header as a standard method of indicating
> compression applied to content information. HTTP servers use this header to
> indicate response compression, and some servers can support receiving HTTP
> requests compressed using Gzip.
> The {{ListenHTTP}} Processor supports receiving Gzip-compressed requests
> using a non-standard header named {{{}flowfile-gzipped{}}}, which the
> deprecated {{PostHTTP}} Processor applies when enabling the {{Compression
> Level}} property.
> The {{ListenHTTP}} Processor should be updated to support handling Gzip
> request compression using the standard {{Content-Encoding}} header, and the
> {{InvokeHTTP}} should be updated to support enabling Gzip.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
