HTTP and HTTPS example application for mbed OS 5
Table of Contents
This application demonstrates how to make HTTP and HTTPS requests and parse the response from Mbed OS 5.
It consists of six demo's, which you can select in
- HTTP demo:
- HTTPS demo:
- Does a GET request to https:os.mbed.com/media/uploads/mbed_official/hello.txt.
- Does a POST request to https:httpbin.org/post.
- HTTP demo with socket re-use.
- HTTPS demo with socket re-use.
- HTTP demo over IPv6.
- HTTPS demo with chunked requests.
Response parsing is done through 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.
- If you're using WiFi, specify the credentials in
- Build the project in the online compiler or using Mbed CLI.
- Flash the project to your development board.
- Attach a serial monitor to your board to see the debug messages.
Defining the network interface¶
This application uses the on-board network interface for your board. If you use an external network interface (f.e. a WiFi module) you need to add the driver to this project. Then, open
network-helper.h and specify which network driver to use.
More information is in the Mbed OS documentation under IP Networking.
Entropy (or lack thereof)¶
On all platforms that do not have the
TRNG feature, 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_TEST_NULL_ENTROPY macros from mbed_app.json.
Default flash size for HTTPS is very large, as the application is loading the default Mbed TLS configuration. To use a more optimized version, you can disable unused cypher suites and other Mbed TLS features with a custom configuration file. Create a new configuration file, then add in
- K64F with Ethernet.
- NUCLEO_F411RE with ESP8266.
- ODIN-W2 with WiFi.
- K64F with Atmel 6LoWPAN shield.
- Mbed Simulator.