Package org.apache.tika.server.core
package org.apache.tika.server.core
-
ClassDescriptionReturns the exception's message in the 400 response body.Last-resort mapper for exceptions no more specific mapper handles, so they don't fall through to CXF's fault chain, which echoes raw exception messages to the caller.JAX-RS filter that gates /config endpoints behind the allowPerRequestConfig flag.Helps produce user facing HTML output.Rejects request bodies larger than
maxRequestSizeBytes(413), still arriving aftermaxRequestReadMillis(408), or that would take the bytes all requests hold pastmaxInFlightRequestBytes(429, seeRequestBodyBudget).Unchecked for the same reason;MaxRequestSizeFilter.RequestBudgetExceededExceptionMappermakes it a 429.Unchecked for the same reason;MaxRequestSizeFilter.RequestTimeoutExceptionMappermakes it a 408.Unchecked so it crosses whatever read path consumes the entity stream;MaxRequestSizeFilter.RequestTooLargeExceptionMapperturns it into the same 413 the declared-Content-Length rejection produces.wrapper class to make isWriteable in MetadataListMBW simplerResource comparator based to produce type.Caps the request-body bytes all in-flight requests hold at once (maxInFlightRequestBytes).Runs on every request as it is received, before resource matching, so it also covers requests CXF answers itself (OPTIONS, 404, 405, ...).Aborts a response still being writtenmaxResponseWriteMillisafter it is committed; the idle timeout alone resets on every trickle a slow reader accepts.Distinct type so its mapper, not the catch-all, handles it.Entity-less: the connection is gone, so CXF has nothing to write; the timer already logged it.Read-only server status for tracking active tasks and statistics.Represents the status of an active task for observability purposes.Simple wrapper exception to be thrown for consistent handling of exceptions that can happen during a parse.One line, no stack trace, per request refused or cut off by a transfer limit (413, 408, 429, aborted response): its own logger, so these client-caused events can be routed or silenced apart from server errors.