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:


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).

Revisions of mbed-http.lib

Revision Date Message Actions
35:4b847971db1b 21 months ago Update to Mbed OS 5.11 File  Diff  Annotate
31:66704f6f17c5 23 months ago Update to new mbed-http, which uses TLSSocket File  Diff  Annotate
28:9bccd981a393 2018-03-27 Compile without requiring RTOS File  Diff  Annotate
27:6554d4f5f1c3 2018-01-25 Fix superfluous \r\n after request body in mbed-http File  Diff  Annotate
25:a8be9f3a530c 2018-01-11 Update mbed-http, add chunked requests File  Diff  Annotate
24:9faf23bbfb7f 2018-01-03 Bump mbed-http - Fix for File  Diff  Annotate
21:903bdf9a49f4 2017-12-15 Update mbed-http File  Diff  Annotate
16:1374b4c35897 2017-09-04 Update mbed-http, was leaking 1024 bytes of memory in tls_socket File  Diff  Annotate
14:3c173847e681 2017-03-30 Bump mbed-http, treat response without Content-Length but with a body as chunked File  Diff  Annotate
13:5a210d227769 2017-03-30 Bump mbed-http File  Diff  Annotate
11:72c089200302 2017-03-28 Add socket reuse File  Diff  Annotate
10:e79a808ebbe8 2017-03-28 Add Lets Encrypt CA, so works again, bump mbed-http File  Diff  Annotate
9:6925d0c8c62f 2017-03-02 Bump mbed-http, now handles URLs without a path File  Diff  Annotate
8:960efb92bd84 2017-03-02 Bump mbed-http, now compiles against ARMCC File  Diff  Annotate
7:5d32909f77de 2017-02-24 Add chunked encoding, make HttpResponse own response headers File  Diff  Annotate
6:4a3ed1515bed 2017-02-23 Bump mbed-http, rely on is_body_complete() in HTTPS requests too File  Diff  Annotate
5:42f713b19337 2017-02-23 Rely on Content-Length, allocate body on the heap File  Diff  Annotate
3:0f5859a9e3de 2017-02-16 Update mbed-http File  Diff  Annotate
2:4b4ac59ff9b0 2017-02-16 Move mbed-http into a separate library File  Diff  Annotate