Configuration of Tika Server 

Setup EXT:tika for Tika Server 

Open Extension settings for EXT:tika General tab and choose "Tika Server" as Extractor.

After that open the Server tab and paste the connection infos/data according fields.

Authentication and timeouts 

The Server tab also offers a few fields to tune the HTTP client used to talk to the Tika Server:

• Username, then Password: credentials for HTTP Basic-Auth, in case the Tika Server is protected by a reverse proxy. Both fields are masked in the Extension Configuration module the same way EXT:tika previously masked the Solr Cell credentials.
• Connect timeout (ms) / Request timeout (ms): how long to wait for the connection to be established, and for the whole request/response, before giving up. Both accept 100 to 60000 milliseconds and are clamped to that range; defaults are 2000 and 10000.

Advanced: raw Guzzle client options 

Everything above only covers the settings most installations need, exposed as typed, validated fields in the Extension Configuration module. For anything else the underlying Guzzle HTTP client supports (TLS verification, a proxy, client certificates, ...), set it directly in your installation's config/system/additional.php (or config/system/settings.php):

$GLOBALS['TYPO3_CONF_VARS']['EXTENSIONS']['tika']['tikaServerGuzzleOptions'] = [
    'verify' => false,
    'proxy' => 'http://proxy.example.com:8080',
    'headers' => [
        'X-My-Custom-Header' => 'foo',
    ],
];

Keys here must already be valid Guzzle request options and take precedence over everything computed from the Extension Configuration module - including overriding the computed auth , connect_timeout or timeout if set explicitly under the same key names.

The array is merged in with \TYPO3\CMS\Core\Utility\ArrayUtility::mergeRecursiveWithOverrule() , the same mechanism TYPO3 itself uses to merge additional.php over LocalConfiguration.php. That means nested options merge key by key instead of being replaced wholesale - the headers example above adds X-My-Custom-Header without losing the default User-Agent header that TYPO3 already sets for every outgoing request.

See Check if it works for test instructions.