[
https://issues.apache.org/jira/browse/TIKA-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14343735#comment-14343735
]
Tim Allison commented on TIKA-964:
----------------------------------
My preference would be to close as "not going to fix" because this focuses on
the older tika-app server, which I'd be game to deprecate and remove in Tika
2.0. The host argument is configurable in the "modern" tika-server/JAX-RS, and
we should encourage users to move to that.
I defer, though, to anyone who feels a need for this in the older server, and
I'd be interested if there's a reason to keep maintaining tika-app's 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)
