[
https://issues.apache.org/jira/browse/TIKA-3320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17302070#comment-17302070
]
Hudson commented on TIKA-3320:
------------------------------
SUCCESS: Integrated in Jenkins build Tika » tika-branch1x-jdk8 #99 (See
[https://ci-builds.apache.org/job/Tika/job/tika-branch1x-jdk8/99/])
TIKA-3320 -- allow case-insensitive header request matching for pdf/ocr config
in tika-server (tallison:
[https://github.com/apache/tika/commit/f5a2aed8ecd209353db831f2013941aed1d5447e])
* (edit)
tika-server/src/main/java/org/apache/tika/server/resource/TikaResource.java
* (edit) tika-server/src/test/java/org/apache/tika/server/TikaResourceTest.java
* (edit) CHANGES.txt
> TikaServer Header Name is Case-sensitive
> ----------------------------------------
>
> Key: TIKA-3320
> URL: https://issues.apache.org/jira/browse/TIKA-3320
> Project: Tika
> Issue Type: Bug
> Components: core, server
> Affects Versions: 1.25
> Reporter: Subhajit Das
> Priority: Minor
> Fix For: 1.26
>
>
> It seems that TikaServer 1.25 header like “X-Tika-PDFOcrStrategy” is case
> sensitive. Same can be confirmed for latest main brunch version.
> This is creating issue in a system where request headers are automatically
> lowercased, before passing down to TikaServer.
>
> According to [https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2]
> "Field names are case-insensitive"
>
> The issue is due to
> First a case-sensitive checking happens for startsWith "X-Tika-PDF" or
> "X-Tika-OCR". Then getDeclaredField of the respective config class is called
> to get field, and invokes the setter method.
> The same is maintained in newer TikaServer.
>
> Possible solution:
> Case-insensitive checking for startsWith. For getDeclaredField we can assume
> only fields will be there (irrespective of case) for any name, and then find
> out the field for it. Then derive setter from actual field name. Invoke the
> same.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
