You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2026/08/05 14:33:00 UTC
[jira] [Commented] (NIFI-16170) Improve Content-Encoding handling for REST API Requests
[ https://issues.apache.org/jira/browse/NIFI-16170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18102098#comment-18102098 ]
ASF subversion and git services commented on NIFI-16170:
--------------------------------------------------------
Commit d47787ab2debc151ed05ee97f143c3743080d470 in nifi's branch refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d47787ab2de ]
NIFI-16170 Improved Content-Encoding handling for REST API (#11509)
- Added consistent handling of multiple Content-Encoding headers
- Excluded all paths from decompression
> Improve Content-Encoding handling for REST API Requests
> -------------------------------------------------------
>
> Key: NIFI-16170
> URL: https://issues.apache.org/jira/browse/NIFI-16170
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Recent changes to the framework REST API moved to using Jetty for handling compression of responses and providing standard responses for requests that proposed unsupported Content-Encoding values.
> Following on from the initial changes, the compression configuration and request filter should be improved with consistent handling of Content-Encoding headers.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)