You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tika.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/05/14 15:52:00 UTC

[jira] [Commented] (TIKA-3357) Remove ambiguity in request handlers

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

ASF GitHub Bot commented on TIKA-3357:
--------------------------------------

lewismc commented on pull request #430:
URL: https://github.com/apache/tika/pull/430#issuecomment-841330165


   @Subhajitdas298 I didn't get a chance to try yet. Does this PR address the annoying logging output we see when starting tika-server?


-- 
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:
users@infra.apache.org


> 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)