[
https://issues.apache.org/jira/browse/TIKA-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17942203#comment-17942203
]
Tim Allison commented on TIKA-4399:
-----------------------------------
Thank you [~tilman] for the heads up on this. The exception makes it look like
it is using an older version of JDBCTableReader before I made the changes on
this ticket. When I look at the code in {{main}}, the updates are there. That's
a TikaInputStream we're now sending into the embedded document util.
> RUnpackExtractor -- improve stream wrapping
> -------------------------------------------
>
> Key: TIKA-4399
> URL: https://issues.apache.org/jira/browse/TIKA-4399
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Major
> Fix For: 4.0.0
>
>
> In the RUnpackExtractor, we create a new TikaInputStream. This can cause
> problems because the security handler no longer tracks bytes read from the
> original stream, and it "thinks" that it is getting a zip bomb.
> In general, I think it would be cleanest to add a {{closeShield}} on
> TikaInputStream so that we're not wrapping it all over the place. We could
> also require that Parsers use a TikaInputStream on embedded files.
> This is a major and breaking change that is ok for 4.x. We should find a less
> disruptive solution for 3.x.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
