[
https://issues.apache.org/jira/browse/NIFI-12637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17808411#comment-17808411
]
ASF subversion and git services commented on NIFI-12637:
--------------------------------------------------------
Commit bf1dfd0615a8c1eb2f8b90480c8a70ca3b86cba4 in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=bf1dfd0615 ]
NIFI-12637 Handle migrating Proxy properties for InvokeHTTP
This closes #8270
Signed-off-by: David Handermann <[email protected]>
> Automatically update InvokeHTTP Proxy configuration properties
> --------------------------------------------------------------
>
> Key: NIFI-12637
> URL: https://issues.apache.org/jira/browse/NIFI-12637
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 2.0.0-M2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Users updating from 1.x are finding that InvokeHTTP is failing because the
> "Proxy Type" property that was previously defined no longer is. As a result,
> InvokeHTTP treats it as a header and attempts to send it as an HTTP Header.
> However, since it has a space in the name, it's invalid and InvokeHTTP fails.
> We should automatically handle migrating the Proxy properties to make this
> seamless.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
