[
https://issues.apache.org/jira/browse/TIKA-3357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17344782#comment-17344782
]
ASF GitHub Bot commented on TIKA-3357:
--------------------------------------
Subhajitdas298 commented on pull request #430:
URL: https://github.com/apache/tika/pull/430#issuecomment-841399256
> @Subhajitdas298 I didn't get a chance to try yet. Does this PR address the
annoying logging output we see when starting tika-server?
Hi, this does not affect any startup logs. This only deals with, choice of
REST handler method. When multiple handlers are valid, say in case of "Accept:
*/*" header, this priority list will decide which one to choose.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Remove ambiguity in request handlers
> ------------------------------------
>
> Key: TIKA-3357
> URL: https://issues.apache.org/jira/browse/TIKA-3357
> Project: Tika
> Issue Type: Improvement
> Components: server
> Affects Versions: 2.0.0, 1.26
> Reporter: Subhajit Das
> Priority: Major
>
> In Tika server, if there is a request with Accept */* or multiple accept,
> that matches with multiple resource handler, then it throws Warning and leads
> to somewhat uncertain handling.
>
> This should be programmatically controlled, to with maintain consistency or
> change standards n future.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
