[
https://issues.apache.org/jira/browse/FLINK-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15633503#comment-15633503
]
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_r86392695
--- Diff: flink-dist/src/main/resources/flink-conf.yaml ---
@@ -60,6 +60,10 @@ parallelism.default: 1
#==============================================================================
# Web Frontend
#==============================================================================
+
+# The address under which the web-based runtime monitor listens.
+
+jobmanager.web.address: 0.0.0.0
--- End diff --
I would leave this commented out as an example configuration option.
> 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)
