[
https://issues.apache.org/jira/browse/NIFI-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15321821#comment-15321821
]
ASF GitHub Bot commented on NIFI-1857:
--------------------------------------
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/497
@markap14 I'm not 100% sure if the change will solve the problem since I
couldn't reproduce the issue myself.
However, I've added additional buffer draining code after receiving EOF
from channel.
In addition to that, a failure detection code was added to check If it
fails sending data as much as expected, when it does, it throws
RuntimeException so that we can investigate further.
Also, I've changed the default nifi.remote.input.secure to `false`.
Could you give it a try once again? If it sill fails, please share your
flow template. Thank you.
> 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)
