[NIFI-2030] Refactor how HTTP-based Site-to-Site ports are communicated

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Won't Do
• Affects Version/s: 1.0.0
• Component/s: Core Framework
• Assignee: Unassigned
• Reporter: Mark Payne
• Created: 15/Jun/16 14:05
• Updated: 03/Jul/18 16:51
• Resolved: 03/Jul/18 16:51

Description

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.

Issue Links

• is related to: NIFI-5146 Ability to configure HTTP and HTTPS simultaneously causes HostHeader issues