From de4e55a16faa206b4b9920e0b3559883184af507 Mon Sep 17 00:00:00 2001 From: Jstsmthrgk <38539927+jstsmthrgk@users.noreply.github.com> Date: Tue, 16 May 2023 23:00:40 +0200 Subject: [PATCH] fix link in WifiClientSecure readme --- libraries/WiFiClientSecure/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/libraries/WiFiClientSecure/README.md b/libraries/WiFiClientSecure/README.md index 906b73b0410..e011d8c3b36 100644 --- a/libraries/WiFiClientSecure/README.md +++ b/libraries/WiFiClientSecure/README.md @@ -34,7 +34,7 @@ certificate for a given server. This allows the client to connect to all public To use this feature in PlatformIO: 1. create a certificate bundle as described in the document below, or obtain a pre-built one you trust: -https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/protocols/esp_crt_bundle.htm +https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/protocols/esp_crt_bundle.html (gen_crt_bundle.py can be found in the /tools folder) a. note: the full bundle will take up around 64k of flash space, but has minimal RAM usage, as only the index of the certificates is kept in RAM @@ -130,4 +130,4 @@ and establishing a secure HTTPS connection with an external server (for example Example of a establishing a secure connection and then showing the fingerprint of the certificate. This can be useful in an IoT setting to know for sure that you are connecting to the right server. Especially in situations where you cannot hardcode a trusted root certificate for long -periods of time (as they tend to get replaced more often than the lifecycle of IoT hardware). \ No newline at end of file +periods of time (as they tend to get replaced more often than the lifecycle of IoT hardware).