[ https://issues.apache.org/jira/browse/NIFI-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319690#comment-15319690 ]
ASF GitHub Bot commented on NIFI-1857: -------------------------------------- Github user ijokarumawak commented on the issue: https://github.com/apache/nifi/pull/497 @markap14 I tested sending data using HTTP Site-to-Site with fresh build of this PR. It successfully sent data. The exception happens when a client sends data packet, but doesn't send additional data packet nor confirm the transaction. It seems Remote Process Group Port stop working in the middle.. I've uploaded my [test flow template and nifi.properties](https://gist.github.com/ijokarumawak/03b781e5dea6e706421fdfabf4b30c8d). The flow should be the same as you mentioned. Would you take a look and let me know if there's any difference. > 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)