Diff: README.md

Revision:

17:97b1dd566b07

Parent:

11:72c089200302

Child:

19:fbf5b033149a

--- a/README.md	Mon Sep 04 16:32:38 2017 +0100
+++ b/README.md	Mon Sep 04 17:01:11 2017 +0100
@@ -15,6 +15,8 @@
 
 Response parsing is done through [nodejs/http-parser](https://github.com/nodejs/http-parser).
 
+**Note:** HTTPS requests do not work on targets with less than 128K of RAM due to the size of the TLS handshake. For more background see [mbed-http](https://developer.mbed.org/teams/sandbox/code/mbed-http).
+
 ## To build
 
 1. Open ``mbed_app.json`` and change the `network-interface` option to your connectivity method ([more info](https://github.com/ARMmbed/easy-connect)).
@@ -24,9 +26,10 @@
 
 ## Entropy (or lack thereof)
 
-On all platforms **except** the FRDM-K64F and FRDM-K22F the application is compiled without TLS entropy sources. This means that your code is inherently unsafe and should not be deployed to any production systems. To enable entropy, remove the `MBEDTLS_NO_DEFAULT_ENTROPY_SOURCES` and `MBEDTLS_TEST_NULL_ENTROPY` macros from mbed_app.json.
+On all platforms **except** the FRDM-K64F, FRDM-K22F and EVK-ODIN-W2, the application is compiled without TLS entropy sources. This means that your code is inherently unsafe and should not be deployed to any production systems. To enable entropy, remove the `MBEDTLS_NO_DEFAULT_ENTROPY_SOURCES` and `MBEDTLS_TEST_NULL_ENTROPY` macros from mbed_app.json.
 
 ## Tested on
 
 * K64F with Ethernet.
 * NUCLEO_F411RE with ESP8266.
+* ODIN-W2 with WiFi.