@drewski7
I have not been able to reproduce the NiFi Registry URL truncation yet using Apache NiFi 1.19 I have installed.
Couple things to check/try:
1. Apache NiFi 1.16.0 is about the time NiFi switched to using the flow.json.gz to load the flow in to memory at startup. Every time you make a change via the NiFi Ui, the current flow.json.gz is archived and new flow.json.gz is created. After fixing your NiFi-Registry URL, go inspect the flow.json.hgz file and see if the URL is being truncated when being persisted out to the flow.json.gz file. This file is only read at startup to load the flow back into NiFi's heap memory. The Registry clients will be at very beginning of the flow.json.gz
2. Try adding the port to the URL and see if that makes a difference (https://xyz.com:443/gateway/registry/nifi-registry-app/nifi-registry-api ).
If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped.
Thank you,
Matt