[
https://issues.apache.org/jira/browse/TIKA-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison resolved TIKA-964.
------------------------------
Resolution: Won't Fix
Let's move users of tika-app's server to Apache CXF's JAX-RS server in the
tika-server module before Tika 2.0. I've entered a bullet on our Tika 2.0
discussion [wiki|http://wiki.apache.org/tika/Tika2_0RoadMap] to remove
tika-app's server in Tika 2.0.
If there is a use case that requires the old tika-app server, please let us
know.
Thank you, [~vitalif], for opening this issue. I'm sorry that it took so long
to respond. Let us know if you have any questions as you migrate over to
tika-server.
> Ability to specify bind address
> -------------------------------
>
> Key: TIKA-964
> URL: https://issues.apache.org/jira/browse/TIKA-964
> Project: Tika
> Issue Type: Improvement
> Components: cli
> Affects Versions: 1.2
> Reporter: Vitaliy Filippov
> Attachments: tika-964.diff
>
>
> Now tika-app listens on all network interfaces, which isn't much secure.
> It would be good to be able to specify the bind address, like:
> java -jar tika-app.jar -p 127.0.0.1:9998
> I'll attach a patch with next comment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
