[
https://issues.apache.org/jira/browse/TIKA-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14701442#comment-14701442
]
Uwe Schindler commented on TIKA-1714:
-------------------------------------
In any case, I agree with Nick, we should not do this. Maybe allow to bind to
all addresses using a System property or allow it to be configured. I have a
lot of machines with multipe IP adresses, and I want external services only
bind to one specific - so default should be ::1 / 127.0.0.1 or any ip adress
the user passes as command line option / system property (like
{{-Djetty.host=XXX -Djetty.port=XXX}}). The use is then also open to bind to
IPv4 and/or IPv6 on his own.
> Consider making default host for Tika Server 0.0.0.0 instead of localhost
> -------------------------------------------------------------------------
>
> Key: TIKA-1714
> URL: https://issues.apache.org/jira/browse/TIKA-1714
> Project: Tika
> Issue Type: Improvement
> Components: server
> Affects Versions: 1.10
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Fix For: 1.11
>
>
> I noticed in Tika-Python on Windows while fixing some bugs that by default
> Tika Server binds to localhost which means that the Tika Server running on
> Windows isn't available to external hosts trying to access it on <host
> name>:9998. I think the default behavior is that it *should* be available
> externally, meaning, we should probably bind to the special address, 0.0.0,0
> which binds to all interfaces.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
