[
https://issues.apache.org/jira/browse/NIFI-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy LoPresto resolved NIFI-5559.
---------------------------------
Resolution: Won't Fix
Assignee: Andy LoPresto
The {{GetHTTP}} and {{PutHTTP}} processors are being deprecated and the
*Trusted Hostname* property is being removed from {{InvokeHTTP}}.
> Allow usage of Trusted Hostname on all HTTP-accessing processors
> ----------------------------------------------------------------
>
> Key: NIFI-5559
> URL: https://issues.apache.org/jira/browse/NIFI-5559
> Project: Apache NiFi
> Issue Type: Wish
> Components: Core Framework
> Affects Versions: 1.7.1
> Reporter: Colin Dean
> Assignee: Andy LoPresto
> Priority: Major
> Labels: http, https, tls
>
> I've used several PutHTTP and GetHTTP processors in a workflow for
> development before realizing that I cannot configure a {{Trusted Hostname}}
> property for those like I can for InvokeHTTP. Configuration and setup
> limitations of the SSLContextService have me wanting to avoid it at all costs.
> I think the workaround is to use InvokeHTTP in place of the others but it'd
> be nice to be able to set a trusted hostname anywhere that an
> SSLContentService can be used.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
