Skip to content

Commit 543ce1d

Browse files
committed
fix doc link
1 parent ab954f7 commit 543ce1d

File tree

1 file changed

+1
-1
lines changed
  • docs/reference/transport/rest5-client/config

1 file changed

+1
-1
lines changed

docs/reference/transport/rest5-client/config/others.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ navigation_title: More config options
44

55
# Other configuration options in the {{es}} Java REST 5 client
66

7-
For any other required configuration needed, the Apache HttpAsyncClient docs should be consulted: [https://hc.apache.org/httpcomponents-asyncclient-4.1.x/](https://hc.apache.org/httpcomponents-asyncclient-4.1.x/) .
7+
For any other required configuration needed, the Apache HttpAsyncClient docs should be consulted: [https://hc.apache.org/httpcomponents-client-5.5.x/](https://hc.apache.org/httpcomponents-client-5.5.x/) .
88

99
::::{note}
1010
If your application runs under the security manager you might be subject to the JVM default policies of caching positive hostname resolutions indefinitely and negative hostname resolutions for ten seconds. If the resolved addresses of the hosts to which you are connecting the client to vary with time then you might want to modify the default JVM behavior. These can be modified by adding [`networkaddress.cache.ttl=<timeout>`](https://docs.oracle.com/javase/8/docs/technotes/guides/net/properties.md) and [`networkaddress.cache.negative.ttl=<timeout>`](https://docs.oracle.com/javase/8/docs/technotes/guides/net/properties.md) to your [Java security policy](https://docs.oracle.com/javase/8/docs/technotes/guides/security/PolicyFiles.md).

0 commit comments

Comments
 (0)