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

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

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

Subhajitdas298 opened a new pull request #427:
URL: https://github.com/apache/tika/pull/427


   Added Resource comparator based to produce type.
   In an ambiguous call, request handler will be chosen based on the type of data it returns.
   
   **Current priority is set as:**
   MediaType.TEXT_PLAIN_TYPE,
   MediaType.APPLICATION_JSON_TYPE,
   MediaType.TEXT_XML_TYPE,
   MediaType.TEXT_HTML_TYPE
   **The lower in list (higher index value), the higher priority it has.**
   In case of no matching in this list, it will be treated as media type all.
   
   **_Note: Please change priority list if some other order is more suitable._**


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