[
https://issues.apache.org/jira/browse/NIFI-11051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17678652#comment-17678652
]
ASF subversion and git services commented on NIFI-11051:
--------------------------------------------------------
Commit 90677742371e4e77fb0b39334961bba102716553 in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=9067774237 ]
NIFI-11051 Corrected handling of empty Registry host property
Signed-off-by: Pierre Villard <[email protected]>
This closes #6842.
> Registry Server defaults to 127.0.0.1 for Empty Host Property
> -------------------------------------------------------------
>
> Key: NIFI-11051
> URL: https://issues.apache.org/jira/browse/NIFI-11051
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.19.0
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Minor
> Fix For: 1.20.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> NiFi Registry 1.19.0 included updates to support HTTP/2 through configurable
> properties. The implementation included a refactored approach to Jetty Server
> Connector configuration. The default {{nifi-registry.properties}} has an
> empty value for {{{}nifi.registry.web.http.host{}}}, which the Jetty Server
> Connector handles as defaulting to listen on the localhost address.
> Prior to this refactoring, the NiFi Registry configuration did not set the
> Server Connector host property when it was empty, which allowed the default
> behavior of listening on all interfaces.
> It is possible to work this problem using {{0.0.0.0}} as the value of the
> host property, but the behavior should be changed to match the historical
> implementation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
