HTTPS Client

The HTTPS Client sample demonstrates a minimal implementation of HTTP communication. It shows how to set up a TLS session towards an HTTPS server and how to send an HTTP request.

Cellular connectivity is supported on the nRF91 Series SiPs, while Wi-Fi® connectivity is supported on the nRF52 or nRF53 Series SoCs hosting the nRF70 Series Wi-Fi companion ICs.

The sample uses the connection manager that provides a common connectivity API for LTE and Wi-Fi stacks.


The sample supports the following development kits:

Hardware platforms


Board name

Build target

nRF9161 DK




nRF9160 DK




nRF9151 DK




nRF7002 DK




When built for an _ns build target, the sample is configured to compile and run as a non-secure application with Cortex-M Security Extensions enabled. Therefore, it automatically includes Trusted Firmware-M that prepares the required peripherals and secure services to be available for the application.


The sample first initializes the Modem library and AT communications. Next, it provisions a root CA certificate to the modem using the Modem key management library. When using an nRF91 Series device, the provisioning must be done before connecting to the LTE network, because the certificates can only be provisioned when the device is not connected.

The sample then establishes a connection to the network, sets up the necessary TLS socket options, and connects to an HTTPS server. It sends an HTTP HEAD request and prints the response code in the terminal.

Obtaining a certificate

The sample connects to, which requires an X.509 certificate. This certificate is provided in the samples/net/https_client/cert folder. The certificate is automatically converted to a HEX format in the CMakeLists.txt file. The generated .inc file is then included in the code, where it is provisioned to the modem.

To connect to other servers, you might need to provision a different certificate. See Certificates for more information.

Using Mbed TLS and TF-M on nRF91 Series DKs

This sample supports using Mbed TLS and Trusted Firmware-M (TF-M). Instead of offloading the TLS sockets into the modem, you can use the Mbed TLS library from Zephyr. Using the Zephyr Mbed TLS, you can still use the offloaded sockets. Mbed TLS offers more configuration options than using the offloaded TLS handling.

When using TF-M and Mbed TLS with PSA crypto, all the crypto operations are run on the secure side on the device.


Configuring Wi-Fi access point credentials

This sample uses the Wi-Fi credentials library to manage Wi-Fi credentials. Before the sample can connect to a Wi-Fi network, you must configure at least one credential set.

Once you have flashed your device with this sample, connect to your device’s UART interface and add credentials using the following command:

wifi_cred add NetworkSSID SecurityMode (OPEN, WPA2-PSK, WPA2-PSK-SHA256, WPA3-SAE) NetworkPassword

Where NetworkSSID is replaced with the SSID of the Wi-Fi access point you want your device to connect to, and NetworkPassword is its password. If you are not sure which security mode to use, enable the CONFIG_NET_L2_WIFI_SHELL Kconfig option and use the wifi scan command to display a list of all accessible networks along with their corresponding security modes. Then either reboot the device or use the wifi_cred auto_connect command to manually trigger a connection attempt.

From now on, these credentials will be automatically used when the configured network is reachable.

When building as firmware image for a non-secure build target, the Wi-Fi credentials backend will be set to PSA using TF-M.

See the Wi-Fi: Shell sample document for more details on the wifi_cred command.

Wi-Fi static credential options

If you want to configure the credentials statically, set the CONFIG_WIFI_CREDENTIALS_STATIC Kconfig option to y.


Do not use static credentials in production environments.

Other options for statically configuring your Wi-Fi credentials:

Sending traces over UART on an nRF91 Series DK

To send modem traces over UART on an nRF91 Series DK, configuration must be added for the UART device in the devicetree and Kconfig. This is done by adding the modem trace UART snippet when building and programming.

Use the Cellular Monitor app for capturing and analyzing modem traces.

TF-M logging must use the same UART as the application. For more details, see shared TF-M logging.

Building and running

This sample can be found under samples/net/https_client in the nRF Connect SDK folder structure.

When built as firmware image for the _ns build target, the sample has Cortex-M Security Extensions (CMSE) enabled and separates the firmware between Non-Secure Processing Environment (NSPE) and Secure Processing Environment (SPE). Because of this, it automatically includes the Trusted Firmware-M (TF-M). To read more about CMSE, see Processing environments.

To build the sample with Visual Studio Code, follow the steps listed on the How to build an application page in the nRF Connect for VS Code extension documentation. See Configuring and building an application for other building scenarios, Programming an application for programming steps, and Testing for general information about testing and debugging in the nRF Connect SDK.

To build the sample with Mbed TLS and TF-M for the nRF91 Series DKs, add the following to your west build command:


The default packet data network (PDN) configuration is dual stack, which will use an IPv6 address if available (and IPv4 if not).

On the nRF91 Series DKs, for testing IPv4 only, you might need to configure the packet data network settings, adding the following to your build command:



After programming the sample to your development kit, test it by performing the following steps:

  1. Connect the USB cable and power on or reset your DK.

  2. Open a terminal emulator and observe that the sample starts, provisions certificates, connects to the network and to, and then sends an HTTP HEAD request.

  3. Observe that the HTTP HEAD request returns HTTP/1.1 200 OK.

Sample output

Output for the default configuration (dual stack, IPV4V6) where the carrier does not support IPv6:

HTTPS client sample started
Certificate match
Waiting for network.. PDP context 0 activated
Waiting for IPv6..
IPv6 not available
Looking up
Resolved (AF_INET)
Connecting to
Sent 61 bytes
Received 370 bytes

>        HTTP/1.1 200 OK

Finished, closing socket.
PDP context 0 deactivated

Output for the default configuration, where the carrier does support IPv6:

HTTPS client sample started
Bringing network interface up
Provisioning certificate
Certificate match
Connecting to the network
Looking up
Resolved 2606:2800:220:1:248:1893:25c8:1946 (AF_INET6)
Connecting to
Sent 61 bytes
Received 370 bytes

>        HTTP/1.1 200 OK

Finished, closing socket.
PDP context 0 deactivated

Output where you override the default packet data network (PDN) configuration to IPv4 only, using the overlay-pdn-nrf91-ipv4.conf overlay:

HTTPS client sample started
Bringing network interface up
Provisioning certificate
Looking up
Resolved (AF_INET)
Connecting to
Sent 61 bytes
Received 370 bytes

>        HTTP/1.1 200 OK

Finished, closing socket.


This sample uses the following nRF Connect SDK libraries:

It uses the following sdk-nrfxlib library:

In addition, it uses the following secure firmware component:

This sample also offers a possibility to use the TF-M module that is at modules/tee/tfm/ in the nRF Connect SDK folder structure.