[
https://issues.apache.org/jira/browse/TIKA-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17304396#comment-17304396
]
Hudson commented on TIKA-3325:
------------------------------
SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk8 #175 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/175/])
TIKA-3325 -- writeLimit is now calculated on the full file (container and
embedded documents), no longer on (tallison:
[https://github.com/apache/tika/commit/f58a27cd392e5e8417dec22fda80450d7310a5ef])
* (edit)
tika-core/src/main/java/org/apache/tika/sax/BasicContentHandlerFactory.java
* (edit)
tika-server/tika-server-classic/src/test/java/org/apache/tika/server/classic/RecursiveMetadataResourceTest.java
* (edit)
tika-core/src/main/java/org/apache/tika/parser/RecursiveParserWrapper.java
* (add) tika-core/src/main/java/org/apache/tika/exception/WriteLimitReached.java
* (edit) tika-core/src/main/java/org/apache/tika/sax/SecureContentHandler.java
* (edit) CHANGES.txt
> 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)
