HTTP client settings

You can configure here some advanced settings of the clients used by YaCy to handle outgoing HTTP connections.

About Server Name Indication (SNI) : this extension to the TLS protocol must be enabled to load some https URLs (for websites deployed with different certificates and host names on the same shared IP address), otherwise loading fails with errors such as Received fatal alert: handshake_failure. But it can be necessary to disable it in order to load some https URLs served by old and misconfigured web servers, otherwise loading fails with the exception javax.net.ssl.SSLProtocolException: "handshake alert: unrecognized_name". Controlling SNI extension activation can also be done with the JVM option jsse.enableSNIExtension, but in that case a server restart is required when you want to modify the setting and it is not customizable per http client (general or for remote Solr).

General HTTP client

Configuration settings for the main HTTP client, used notably to crawl websites and communicate with other YaCy peers.

#(http.outgoing.general.tls.sniExtension.enabled.readonly)#::

SNI extension support can not be defined here as it is currently configured by the JVM option -Djsse.enableSNIExtension=#[jvmSettingValue]#.

#(/http.outgoing.general.tls.sniExtension.enabled.readonly)#

Enable SNI extension to TLS

Remote Solr HTTP client

Configuration settings for the specific HTTP client dedicated to communications with remote Solr servers (located on other YaCy peers or eventually owned by this one when it is configured to use a remote Solr index).

#(http.outgoing.remoteSolr.tls.sniExtension.enabled.readonly)#::

SNI extension support can not be defined here as it is currently configured by the JVM option -Djsse.enableSNIExtension=#[jvmSettingValue]#.

#(/http.outgoing.remoteSolr.tls.sniExtension.enabled.readonly)#

Enable SNI extension to TLS

Changes will take effect immediately.