You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tika.apache.org by "Tim Allison (Jira)" <ji...@apache.org> on 2021/03/16 14:05:00 UTC

[jira] [Commented] (TIKA-3325) Add header to limit extracted content

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

Tim Allison commented on TIKA-3325:
-----------------------------------

[~julienFL] I'm sorry for not realizing this.  {{rmeta}} does currently have and use {{writeLimit}}.  The problem is that this is enforced _per_ container document/embedded document.  It isn't enforced across all content in a container file.  If you want an overall limit on all content per container file, I can try to bolt that on... {{writeLimitTotal}}?

> Add header to limit extracted content
> -------------------------------------
>
>                 Key: TIKA-3325
>                 URL: https://issues.apache.org/jira/browse/TIKA-3325
>             Project: Tika
>          Issue Type: Improvement
>          Components: server
>    Affects Versions: 1.24.1
>            Reporter: Julien Massiera
>            Priority: Major
>
> In Tika server, it would be very useful to handle a new header in the requests of the /rmeta endpoint, that would allow to define a bytes limitation of the data content extracted from documents.
> For example the header "writeLimit: 1000000" would guarantee that the "X-TIKA:content" metadata object would not exceed 1000000 bytes



--
This message was sent by Atlassian Jira
(v8.3.4#803005)