[
https://issues.apache.org/jira/browse/TIKA-4848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18108968#comment-18108968
]
ASF GitHub Bot commented on TIKA-4848:
--------------------------------------
tballison opened a new pull request, #3085:
URL: https://github.com/apache/tika/pull/3085
…lly so readers never see a partial output
This is to prevent a flaky unit test we're now seeing in tika-server-core in
ci.
> Enable redaction of exception messages and/or full stack traces
> ---------------------------------------------------------------
>
> Key: TIKA-4848
> URL: https://issues.apache.org/jira/browse/TIKA-4848
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Minor
>
> Exception messages can sometimes include confidential information.
> In 3.x, we had stacktrace on/off in tika-server, but then we included the
> full stacktrace for embedded files.
> We should have one policy throughout the parse life cycle, including in
> tika-server.
> I propose three options:
> 1) Full stacktrace (as we have now)
> 2) Redacted message, but the rest of the stacktrace
> 3) Fully redacted stacktrace (maybe just the class).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
