[
https://issues.apache.org/jira/browse/FLINK-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15633506#comment-15633506
]
ASF GitHub Bot commented on FLINK-4876:
---------------------------------------
Github user uce commented on a diff in the pull request:
https://github.com/apache/flink/pull/2680#discussion_r86392650
--- Diff:
flink-core/src/main/java/org/apache/flink/configuration/ConfigConstants.java ---
@@ -1193,7 +1195,12 @@
// ------------------------- JobManager Web Frontend
----------------------
-
+
+ /** The config key for the address of the JobManager web frontend. */
+ public static final ConfigOption<String>
DEFAULT_JOB_MANAGER_WEB_FRONTEND_ADDRESS =
+ key("jobmanager.web.address")
+ .defaultValue("0.0.0.0");
--- End diff --
I'm wondering whether it's better to have `null` as default and simply let
InetAddress pick the address. I don't know if it makes a difference at the end.
> Allow web interface to be bound to a specific ip/interface/inetHost
> -------------------------------------------------------------------
>
> Key: FLINK-4876
> URL: https://issues.apache.org/jira/browse/FLINK-4876
> Project: Flink
> Issue Type: Improvement
> Components: Webfrontend
> Affects Versions: 1.2.0, 1.1.2, 1.1.3
> Reporter: Bram Vogelaar
> Assignee: Bram Vogelaar
> Priority: Minor
>
> Currently the web interface automatically binds to all interfaces on 0.0.0.0.
> IMHO there are some use cases to only bind to a specific ipadress, (e.g.
> access through an authenticated proxy, not binding on the management or
> backup interface)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
