[ https://issues.apache.org/jira/browse/TIKA-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14701330#comment-14701330 ]
Nick Burch commented on TIKA-1714: ---------------------------------- See TIKA-1196 for previous discussions on localhost vs bind to everything + available potentially to all > 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)