You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Mark Payne (JIRA)" <ji...@apache.org> on 2016/06/15 14:06:09 UTC

[jira] [Created] (NIFI-2030) Refactor how HTTP-based Site-to-Site ports are communicated

Mark Payne created NIFI-2030:
--------------------------------

             Summary: Refactor how HTTP-based Site-to-Site ports are communicated
                 Key: NIFI-2030
                 URL: https://issues.apache.org/jira/browse/NIFI-2030
             Project: Apache NiFi
          Issue Type: Task
          Components: Core Framework
    Affects Versions: 1.0.0
            Reporter: Mark Payne
             Fix For: 1.0.0


Currently, when clustered, the NodeIdentifier contains a field siteToSiteHttpApiPort but site-to-site should be enabled on both HTTP and HTTPS interfaces if both are made available. We should refactor NodeIdentifier so that it contains an apiPort and a secureApiPort and then when asked for the list of Peers for site-to-site, it should use the scheme of the given HTTP request to determine which port to return. I.e., if the request was made to https://myhost:443/site-to-site/peers then we should return the secure api port. If made to http://myhost:80/site-to-site/peers then we should return the non-secure api port.

The fix version for this is marked as 1.0.0, but this should be backward compatible, so if it needs to slide from 1.0.0 it's not critical that it make it into this version.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)