[
https://issues.apache.org/jira/browse/NIFI-10161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17558920#comment-17558920
]
ASF subversion and git services commented on NIFI-10161:
--------------------------------------------------------
Commit d8ebfb25d09536a9201959c0e1d4e2454ca68c64 in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d8ebfb25d0 ]
NIFI-10161 Added Gzip Content-Encoding to InvokeHTTP and ListenHTTP
Signed-off-by: Pierre Villard <[email protected]>
This closes #6150.
> 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
> Time Spent: 10m
> 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.7#820007)
