[
https://issues.apache.org/jira/browse/KAFKA-8312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Magesh kumar Nandakumar updated KAFKA-8312:
-------------------------------------------
Priority: Minor (was: Major)
> Rest advertised name is required while setting the listener to 0.0.0.0
> ----------------------------------------------------------------------
>
> Key: KAFKA-8312
> URL: https://issues.apache.org/jira/browse/KAFKA-8312
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
> Affects Versions: 1.1.0
> Reporter: Magesh kumar Nandakumar
> Assignee: Magesh kumar Nandakumar
> Priority: Minor
>
> [https://cwiki.apache.org/confluence/display/KAFKA/KIP-208%3A+Add+SSL+support+to+Kafka+Connect+REST+interface]
> added the support for SSL and as part of it introduced a listener config.
> Prior to the change, one could specify not specify a `host.name` config and
> they would bind to default interface and this worked well for not requiring
> to configure the `rest.advertised.host.name` explicitly. If one has to use
> https they could still bind to default interface by not specifying the
> hostname but when you use 0.0.0.0 as the host in listeners, you are required
> to set the advertised.host.name explicitly. Connect framework can either use
> InetAddress.getLocalHost().getCanonicalHostName() as the default value or use
> the above only when the listeners host is 0.0.0.0. This might be an useful
> improvement while configuring connectors to listen on all network interfaces.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
