[
https://issues.apache.org/jira/browse/MTOMCAT-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13752414#comment-13752414
]
Daniel Cassidy commented on MTOMCAT-92:
---------------------------------------
It's precisely because tomcat-maven-plugin is used during development that it
is important to bind to the loopback interface only. To do otherwise exposes
development code to the network and is a security risk.
Binding to loopback only ought to have been the default.
> Bind tomcat to a self-chosen network interface
> ----------------------------------------------
>
> Key: MTOMCAT-92
> URL: https://issues.apache.org/jira/browse/MTOMCAT-92
> Project: Apache Tomcat Maven Plugin
> Issue Type: Bug
> Affects Versions: 1.1
> Reporter: Björn Michael
> Assignee: Olivier Lamy (*$^¨%`£)
> Fix For: backlog
>
>
> Tomcat is bound to 0.0.0.0 (all interfaces) by default. I feel the need to
> change this binding to e.g. localhost (127.0.0.1) or another interface by
> adding a <host>127.0.0.1</host> to plugin configuration in pom.xml. This is
> often necessary for security or firewall reasons during the development of
> web applications.
> Thanks in advance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
