tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris A. Mattmann (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TIKA-1714) Consider making default host for Tika Server instead of localhost
Date Tue, 18 Aug 2015 14:05:45 GMT

    [ https://issues.apache.org/jira/browse/TIKA-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14701297#comment-14701297

Chris A. Mattmann commented on TIKA-1714:

Hey Nick - this is an orthogonal change. The server would still bind to localhost, and any
local network interfaces on the machine (e.g..,, localhost, <your machine's IP>,

> Consider making default host for Tika Server 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

View raw message