[
https://issues.apache.org/jira/browse/TIKA-4848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18109979#comment-18109979
]
Hudson commented on TIKA-4848:
------------------------------
SUCCESS: Integrated in Jenkins build Tika ยป tika-main-jdk17 #1602 (See
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk17/1602/])
TIKA-4848 pipes, step 3 (#3087) (github:
[https://github.com/apache/tika/commit/05267dd00f8a59f83ee9ba20bd7cdbb35bf77155])
* (edit)
tika-pipes/tika-pipes-core/src/main/java/org/apache/tika/pipes/core/server/ServerProtocolIO.java
* (edit)
tika-pipes/tika-pipes-core/src/main/java/org/apache/tika/pipes/core/server/PipesWorker.java
* (edit)
tika-pipes/tika-pipes-core/src/main/java/org/apache/tika/pipes/core/server/FetchHandler.java
* (edit)
tika-pipes/tika-pipes-core/src/main/java/org/apache/tika/pipes/core/server/PipesServer.java
* (edit)
tika-pipes/tika-pipes-core/src/test/java/org/apache/tika/pipes/core/server/ServerProtocolIOTest.java
* (edit)
tika-pipes/tika-pipes-core/src/main/java/org/apache/tika/pipes/core/server/ConnectionHandler.java
* (edit)
tika-pipes/tika-pipes-core/src/main/java/org/apache/tika/pipes/core/server/EmitHandler.java
* (add)
tika-pipes/tika-pipes-integration-tests/src/test/java/org/apache/tika/pipes/core/ExceptionReportingPipesTest.java
* (edit)
tika-pipes/tika-pipes-core/src/main/java/org/apache/tika/pipes/core/server/SharedServerResources.java
* (add)
tika-pipes/tika-pipes-integration-tests/src/test/resources/test-documents/mock-npe.xml
* (edit) CHANGES.txt
* (add)
tika-pipes/tika-pipes-integration-tests/src/test/resources/configs/tika-config-exception-reporting.json
* (edit)
tika-pipes/tika-pipes-core/src/main/java/org/apache/tika/pipes/core/server/ParseHandler.java
TIKA-4848: server, step 4 (#3106) (github:
[https://github.com/apache/tika/commit/72f4df7cb1038516e976496d42b9ceaf82325efe])
* (edit) CHANGES.txt
* (edit)
tika-server/tika-server-core/src/main/java/org/apache/tika/server/core/resource/MetadataResource.java
* (edit) docs/modules/ROOT/pages/security.adoc
* (add)
tika-server/tika-server-core/src/test/java/org/apache/tika/server/core/RedactedStackTraceTest.java
* (edit)
tika-server/tika-server-core/src/main/java/org/apache/tika/server/core/TikaServerParseExceptionMapper.java
* (edit) docs/modules/ROOT/pages/configuration/index.adoc
* (edit)
tika-server/tika-server-core/src/main/java/org/apache/tika/server/core/resource/TikaResource.java
* (edit) docs/modules/ROOT/pages/advanced/setting-limits.adoc
* (edit)
tika-server/tika-server-core/src/test/resources/config-examples/server-basic.json
* (edit) docs/modules/ROOT/pages/using-tika/server/index.adoc
* (edit)
tika-server/tika-server-core/src/main/java/org/apache/tika/server/core/TikaServerProcess.java
* (add)
tika-server/tika-server-core/src/test/java/org/apache/tika/server/core/TikaServerParseExceptionMapperTest.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)
