[
https://issues.apache.org/jira/browse/TIKA-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551093#comment-17551093
]
Tim Allison commented on TIKA-3786:
-----------------------------------
In looking back at fillMetadata, users can do this now with "meta_" prefixed
headers, but I'd still prefer to treat {{Content-Length}} as a first class
citizen.
> 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
>
> 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)