[
https://issues.apache.org/jira/browse/TIKA-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551151#comment-17551151
]
Hudson commented on TIKA-3786:
------------------------------
SUCCESS: Integrated in Jenkins build Tika ยป tika-main-jdk8 #631 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/631/])
TIKA-3786: Allow pass-through of 'Content-Length' header to metadata in
TikaResource (tallison:
[https://github.com/apache/tika/commit/db4092d23418a768d7cd01745fc956be0a80ed39])
* (edit) tika-core/src/main/java/org/apache/tika/parser/AutoDetectParser.java
* (edit) CHANGES.txt
* (edit)
tika-server/tika-server-core/src/main/java/org/apache/tika/server/core/resource/TikaResource.java
> Allow pass-through of content-length to metadata in TikaResource
> ----------------------------------------------------------------
>
> Key: TIKA-3786
> URL: https://issues.apache.org/jira/browse/TIKA-3786
> Project: Tika
> Issue Type: Improvement
> Reporter: Tim Allison
> Priority: Trivial
> Fix For: 2.4.1
>
>
> The AutoDetectParserConfig allows users to specify a length threshold at
> which to spool a file to disk. The AutoDetectParser checks the
> {{Content-Length}} in the metadata object, and if it exists and is larger
> than the threshold, the AutoDetectParser will spool the file to disk. The
> spooling is already largely taken care of in the pipes handlers, but it isn't
> available yet in the legacy /tika or /rmeta endpoints via TikaResource or
> RecursiveMetadataResource.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
