Skip to content

Commit 9aa1e19

Browse files
tballisonCopilot
andauthored
Potential fix for pull request finding
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
1 parent 658aa5b commit 9aa1e19

1 file changed

Lines changed: 6 additions & 2 deletions

File tree

docs/modules/ROOT/pages/migration-to-4x/migrating-tika-server-4x.adoc

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -92,13 +92,17 @@ The separate `/config` endpoints have been removed. Configuration is now handled
9292
=== Error Response Bodies Are Now JSON
9393
9494
In 3.x, error responses from `/tika`, `/rmeta`, and `/unpack` returned a plain-text
95-
body such as `"Parse failed: TIMEOUT"`. In 4.x these endpoints return a JSON body:
95+
body such as "Parse failed: TIMEOUT". In 4.x these endpoints return a JSON body with
96+
at least a `status` field:
9697
9798
[source,json]
9899
----
99-
{"status": "TIMEOUT", "message": "Task timed out after 60000ms"}
100+
{"status": "TIMEOUT"}
100101
----
101102
103+
When the server is configured with `returnStackTrace=true`, a `message` field is also
104+
included (it may contain a server-side stack trace), e.g. `{"status": "TIMEOUT", "message": "Task timed out after 60000ms"}`.
105+
102106
The HTTP status codes are also more precise:
103107
104108
* `UNSPECIFIED_CRASH` changed from `500` to `503` — it is a transient process failure

0 commit comments

Comments
 (0)