[
https://issues.apache.org/jira/browse/NIFI-4790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16337405#comment-16337405
]
ASF GitHub Bot commented on NIFI-4790:
--------------------------------------
Github user ijokarumawak commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2426#discussion_r163515579
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/InvokeHTTP.java
---
@@ -213,11 +219,21 @@
public static final PropertyDescriptor PROP_SSL_CONTEXT_SERVICE = new
PropertyDescriptor.Builder()
.name("SSL Context Service")
- .description("The SSL Context Service used to provide client
certificate information for TLS/SSL (https) connections.")
+ .description("The SSL Context Service used to provide client
certificate information for TLS/SSL (https) connections."
+ + " It is also used to connect to HTTPS Proxy.")
.required(false)
.identifiesControllerService(SSLContextService.class)
.build();
+ public static final PropertyDescriptor PROP_PROXY_TYPE = new
PropertyDescriptor.Builder()
--- End diff --
Probably we should support Expression Language with "Proxy Type" because
Proxy host and port do so.
> Support HTTPS proxy in InvokeHTTP
> ---------------------------------
>
> Key: NIFI-4790
> URL: https://issues.apache.org/jira/browse/NIFI-4790
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Marco Gaido
> Assignee: Marco Gaido
> Priority: Major
>
> InvokeHTTP currently assumes that the proxy (if set) uses HTTP. We should
> introduce a new property to indicate the protocol used by the proxy (either
> http or https) in order to support also HTTPS proxies.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
