[
https://issues.apache.org/jira/browse/NIFI-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15317960#comment-15317960
]
ASF GitHub Bot commented on NIFI-1857:
--------------------------------------
Github user ijokarumawak commented on a diff in the pull request:
https://github.com/apache/nifi/pull/497#discussion_r66016174
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-resources/src/main/resources/conf/nifi.properties
---
@@ -111,9 +111,11 @@
nifi.components.status.repository.buffer.size=${nifi.components.status.repositor
nifi.components.status.snapshot.frequency=${nifi.components.status.snapshot.frequency}
# Site to Site properties
-nifi.remote.input.socket.host=
-nifi.remote.input.socket.port=
+nifi.remote.input.host=
nifi.remote.input.secure=true
+nifi.remote.input.socket.port=
+nifi.remote.input.http.enabled=true
--- End diff --
`nifi.remote.input.http.enabled` and `nifi.remote.input.secure` are set to
true by default, but https port, keystore and truststore are not configured.
With the default nifi.properties file, user will see following exception at
start up, which is not a good UX. Can we change default
`nifi.remote.input.secure` to `false` ?
```
Caused by: java.lang.RuntimeException: Remote input HTTPS is enabled but
nifi.web.https.port is not specified.
at
org.apache.nifi.util.NiFiProperties.getRemoteInputHttpPort(NiFiProperties.java:439)
~[nifi-properties-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
```
> Support HTTP(S) as a transport mechanism for Site-to-Site
> ---------------------------------------------------------
>
> Key: NIFI-1857
> URL: https://issues.apache.org/jira/browse/NIFI-1857
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Koji Kawamura
> Assignee: Koji Kawamura
> Original Estimate: 480h
> Remaining Estimate: 480h
>
> We should add support for using HTTP(S) for site-to-site to be an alternative
> to the current socket based approach.
> This would support the same push based or pull based approach site-to-site
> offers now but it would use HTTP(S) for all interactions to include learning
> about ports, learning about NCM topology, and actually exchanging data. This
> mechanism should also support interaction via an HTTP proxy.
> This would also require some UI work to allow the user to specify which
> protocol for site-to-site to use such as 'raw' vs 'http'. We also need to
> document any limitations with regard to SSL support for this mode and we'd
> need to provide 'how-to' when using proxies like http_proxy or something else.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
