This is an automated email from the ASF dual-hosted git repository.
tballison pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/tika.git
The following commit(s) were added to refs/heads/main by this push:
new bb1f6f2032 update CHANGES.txt
bb1f6f2032 is described below
commit bb1f6f203259d8dfa8bff9d1067de0a20de55b9c
Author: tallison <[email protected]>
AuthorDate: Fri Sep 25 12:44:41 2026 -0400
update CHANGES.txt
---
CHANGES.txt | 11 +----------
1 file changed, 1 insertion(+), 10 deletions(-)
diff --git a/CHANGES.txt b/CHANGES.txt
index bfef25732b..169c67f16c 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -94,16 +94,7 @@ Release 4.1.0 - 9/25/2026
regardless (TIKA-4931).
* Pipes no longer copies the caller's Content-Type hint back over the
- detected type on output: a PDF sent with Content-Type text/html came
- back labelled text/html. The resource name and Content-Type are parse
- inputs (carried into detection, TIKA-4825) and the parse's own value is
- what comes back; every other caller key is still injected verbatim.
- Affects PipesForkParser and every tika-server forked-parse endpoint.
- tika-server no longer stamps tk:content-type-override from the request
- Content-Type; the worker never carried it. Compat: under CONTENT_ONLY,
- or a metadata filter that excludes them, Content-Type and
- tk:resource-name are now absent from the result rather than the
- caller's own values (TIKA-4932).
+ detected type on output (TIKA-4932).
EXTRACTION AND FORMATS
