[
https://issues.apache.org/jira/browse/NIFI-15030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18024099#comment-18024099
]
ASF subversion and git services commented on NIFI-15030:
--------------------------------------------------------
Commit be650f2443a856292e2f9d8b8f8d84f419a8ce97 in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=be650f2443 ]
NIFI-15030 Filtered blank Header Names from Responses in InvokeHTTP
Closes #10360
Signed-off-by: Mike Moser <[email protected]>
> Filter Blank Header Names from Responses in InvokeHTTP
> ------------------------------------------------------
>
> Key: NIFI-15030
> URL: https://issues.apache.org/jira/browse/NIFI-15030
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In rare situations, HTTP servers can return responses with blank header
> names. This may be the result of malformed response header sections, which
> can lead to attempting to write FlowFile attributes with empty attribute
> names.
> The InvokeHTTP Processor handling of response headers should be updated
> filter out empty response header names, avoiding the potential for invalid
> FlowFile attribute names.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
