From afd790c348ef4c926b156699d44af449ee9dfd3a Mon Sep 17 00:00:00 2001 From: Rotzbua Date: Mon, 4 Dec 2017 10:18:00 +0100 Subject: [PATCH] Update client-secure-examples.rst fix link --- doc/esp8266wifi/client-secure-examples.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/esp8266wifi/client-secure-examples.rst b/doc/esp8266wifi/client-secure-examples.rst index 5d9fd0373f..a21a3e7731 100644 --- a/doc/esp8266wifi/client-secure-examples.rst +++ b/doc/esp8266wifi/client-secure-examples.rst @@ -178,4 +178,4 @@ Conclusion Programming a secure client is almost identical as programming a non-secure client. The difference gets down to one extra step to verify server's identity. Keep in mind limitations due to heavy memory usage that depends on the strength of the key used by the server and whether server is willing to negotiate the `TLS buffer size `__. For the list of functions provided to manage secure clients, please refer to the `Client Secure Class -:arrow\_right: `__ documentation. +:arrow\_right: `__ documentation.