[
https://issues.apache.org/jira/browse/NIFI-10161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17599531#comment-17599531
]
David Handermann commented on NIFI-10161:
-----------------------------------------
Thanks for the feedback on this change [~relaynetwork].
The ListenHTTP Processor includes custom handling for the internal NiFi
FlowFile structure, which was part of the reason for moving to a standard
approach for handling content encoding. The current content negotiation
strategy is not the most efficient for generalized processing, so this may be
worth evaluating more generally.
As this Jira issue is closed, it would be helpful to write up a new issue
summarizing the use case details.
> 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)
