HTTP and HTTPS example application for Mbed OS 5

Dependencies:   mbed-http

This application demonstrates how to make HTTP and HTTPS requests and parse the response from Mbed OS 5.

It consists of six example applications, which you can select in source/select-demo.h:

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.

To build

  1. If you're using WiFi, specify the credentials in mbed_app.json.
  2. Build the project in the online compiler or using Mbed CLI.
  3. Flash the project to your development board.
  4. 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_NO_DEFAULT_ENTROPY_SOURCES and MBEDTLS_TEST_NULL_ENTROPY macros from mbed_app.json.

Flash size

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 mbed_app.json:

"MBEDTLS_CONFIG_FILE=\"mbedtls_config.h\""

to the macros array.

Running tests

You can run the integration tests from this project via Mbed CLI.

  1. In select-demo.h set the DEMO macro to DEMO_TESTS.
  2. Set your WiFi credentials in mbed_app.json.
  3. Then run the tests via:

$ mbed test -v -n mbed-http-tests-tests-*

Tested on

  • K64F with Ethernet.
  • NUCLEO_F411RE with ESP8266 (not working on Mbed OS 5.12+)
  • ODIN-W2 with WiFi.
  • K64F with Atmel 6LoWPAN shield.
  • DISCO-L475VG-IOT01A with WiFi (requires the wifi-ism43362 driver).

History

Update to Mbed OS 5.11 default tip

23 months ago, by Jan Jongboom [Fri, 04 Jan 2019 13:32:26 +0100] rev 35

Update to Mbed OS 5.11


Update os.mbed.com CA

24 months ago, by Jan Jongboom [Wed, 05 Dec 2018 17:16:00 +0900] rev 34

Update os.mbed.com CA


Revert back to DEMO_HTTP

2018-10-30, by Jan Jongboom [Tue, 30 Oct 2018 11:11:11 +0800] rev 33

Revert back to DEMO_HTTP


Update to Mbed OS 5.10, update to use TLSSocket

2018-10-30, by Jan Jongboom [Tue, 30 Oct 2018 11:07:46 +0800] rev 32

Update to Mbed OS 5.10, update to use TLSSocket


Update to new mbed-http, which uses TLSSocket mbed-os-5.10

2018-10-30, by Jan Jongboom [Tue, 30 Oct 2018 11:07:10 +0800] rev 31

Update to new mbed-http, which uses TLSSocket


Update to Mbed OS 5.10, with default network interface mbed-os-5.10

2018-10-29, by Jan Jongboom [Mon, 29 Oct 2018 14:34:43 +0800] rev 30

Update to Mbed OS 5.10, with default network interface


Move serial baud rate config into mbed_app.json

2018-03-27, by Jan Jongboom [Tue, 27 Mar 2018 11:57:33 +0200] rev 29

Move serial baud rate config into mbed_app.json


Compile without requiring RTOS

2018-03-27, by Jan Jongboom [Tue, 27 Mar 2018 11:13:48 +0200] rev 28

Compile without requiring RTOS


Fix superfluous \r\n after request body in mbed-http

2018-01-25, by Jan Jongboom [Thu, 25 Jan 2018 10:15:15 +0200] rev 27

Fix superfluous \r\n after request body in mbed-http


Set demo back to HTTP

2018-01-12, by Jan Jongboom [Fri, 12 Jan 2018 13:45:51 +0100] rev 26

Set demo back to HTTP