[
https://issues.apache.org/jira/browse/TIKA-3357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17325080#comment-17325080
]
Hudson commented on TIKA-3357:
------------------------------
SUCCESS: Integrated in Jenkins build Tika » tika-branch1x-jdk8 #118 (See
[https://ci-builds.apache.org/job/Tika/job/tika-branch1x-jdk8/118/])
[TIKA-3357] removes ambiguity by choosing handler based on produce type (#427)
(github:
[https://github.com/apache/tika/commit/82f7a34b692706ba3eb55b64453cca29203db3e8])
* (add)
tika-server/src/main/java/org/apache/tika/server/ProduceTypeResourceComparator.java
* (edit) tika-server/src/main/java/org/apache/tika/server/TikaServerCli.java
* (edit) tika-server/src/test/java/org/apache/tika/server/CXFTestBase.java
TIKA-3357 -- add unit test (tallison:
[https://github.com/apache/tika/commit/3fa19532b1ec78b57d1e238c2192d54df7572285])
* (edit) tika-server/src/test/java/org/apache/tika/server/TikaResourceTest.java
> 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)
