You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "David Handermann (Jira)" <ji...@apache.org> on 2022/06/23 15:55:00 UTC
[jira] [Created] (NIFI-10161) Add Gzip Request Content-Encoding in InvokeHTTP and ListenHTTP
David Handermann created NIFI-10161:
---------------------------------------
Summary: 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
[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)