janhoy commented on code in PR #3670:
URL: https://github.com/apache/solr/pull/3670#discussion_r2412992252


##########
solr/solr-ref-guide/modules/indexing-guide/pages/indexing-with-tika.adoc:
##########
@@ -391,6 +463,33 @@ This is only required if you have customized your Tika 
implementation.
 +
 Example: `tika.config=/path/to/tika.config`
 
+`tikaserver.timeoutSeconds`::
++
+[%autowidth,frame=none]
+|===
+|Optional |Default: `180` seconds
+|===
++
+Sets the HTTP timeout when communicating with Tika Server, in seconds. Can be 
set per request as a parameter or as a default in the request handler 
configuration. If set on the request it overrides the handler default for that 
call only.
++
+Examples:
++
+- Per request: `tikaserver.timeoutSeconds=60`
+- In `solrconfig.xml`: `<int name="tikaserver.timeoutSeconds">60</int>`
+
+
+`tikaserver.url`::
++
+[%autowidth,frame=none]
+|===
+|Optional |Default: none
+|===
++
+Specifies the URL of the Tika server to use when the `extraction.backend` 
parameter is set to `tikaserver`.
+This parameter is required when using the `tikaserver` backend. This parameter 
can only be configured in the configuration, not per request.
++

Review Comment:
   Instead of building support for HTTPs and custom certs from the beginning, 
let's document the limitation instead:
   
   ```suggestion
   +
   If your TikaServer is using HTTPS, it needs to use a verifiable SSL 
certificate. If using self-signed or custom Certificate Authority, you will 
need to add those to Solr's Truststore. The `tikaserver` backend currently does 
not have support for configuring custom certificates for Tika alone.
   +
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to