[
https://issues.apache.org/jira/browse/TIKA-4848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18109178#comment-18109178
]
Hudson commented on TIKA-4848:
------------------------------
SUCCESS: Integrated in Jenkins build Tika ยป tika-main-jdk17 #1591 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk17/1591/])
[TIKA-4848] Fix expected output in ExceptionUtilsTest to account for Windows
line endings. (#3089) (github:
[https://github.com/apache/tika/commit/ba4d312aafd86c15c715f9b96366ea5b4572b112])
* (edit) tika-core/src/test/java/org/apache/tika/utils/ExceptionUtilsTest.java
> 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)
