Avnet / Mbed OS http-example-wnc

Demonstration program with support for the WNC M14A2A Cellular LTE Data Module added. An additional demonstration program was also added that shows a few other features (for chunked responses).

Dependencies:   easy-connect mbed-http

mbed-os-example-http(s) using WNC 14A2A Data Module

This application builds on the application provided by ARM (see https://developer.mbed.org/teams/sandbox/code/mbed-http/). It demonstrates how to make HTTP and HTTPS requests and parse the response from mbed OS 5.

There are a total of five demo's, which can be selected by modifying source/select-demo.h.

1. HTTP demo (DEMO_HTTP):

• Does a GET request to http://httpbin.org/status/418.
• Does a POST request to http://httpbin.org/post.

2. HTTPS demo (DEMO_HTTPS):

• Does a GET request to https://developer.mbed.org/media/uploads/mbed_official/hello.txt.
• Does a POST request to https://httpbin.org/post.

3. HTTP demo with socket re-use (DEMO_HTTP_SOCKET_REUSE).

• Similar to the HTTP demo but reuses the socket for all interactions

4. HTTPS demo with socket re-use (DEMO_HTTPS_SOCKET_REUSE).

• Similar to the HTTPS demo above

5. HTTP & HTTPS demo with socket re-use and chunked call-backs (DEMO_HTTPx)

• Performs the same calls via HTTP first and HTTPS second
• DOES A socket get from http://developer.mbed.org.
• Does a HTTP_GET from http://developer.mbed.org
• Does a HTTP_POST from http://httpbin.org/post
• Does a HTTP_PUT from http://httpbin.org/put
• Does a HTTP_DELETE from http://httpbin.org/delete
• Does a HTTP_GET from http://httpbin.org/stream
• Does a HTTP_GET from http://httpbin.org/get

Response parsing is done through [nodejs/http-parser](https://github.com/nodejs/http-parser).

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

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.

Tested on

• K64F with Ethernet.
• NUCLEO_F411RE with ESP8266.
• AT&T Cellular IoT Starter Kit with WNC M14A2A Cellular Data Module

The WNCInterface class currently supports the following version(s):

• MPSS: M14A2A_v11.50.164451 APSS: M14A2A_v11.53.164451

License

This library is released under the Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License and may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Increase MBEDTLS_MPI_MAX_SIZE so HTTPS calls to httpbin work as well