Help¶

Size of the data fragments reported to the application when using HTTP or HTTPS. Use the largest fragment size when using HTTPS to reduce the bandwidth overhead due to the HTTP headers, which are sent for each fragment. When using the Modem library and TLS, the fragment size may not exceed 2 kB minus the largest HTTP header the application expects to receive.

Direct dependencies¶

DOWNLOAD_CLIENT

(Includes any dependencies from ifs and menus.)

Default¶

DOWNLOAD_CLIENT_HTTP_FRAG_SIZE_2048

Choice options¶

Kconfig definition¶

At <nRF>/subsys/net/lib/download_client/Kconfig:31

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:23 → <Zephyr>/modules/Kconfig:6 → <BuildDir>/Kconfig/Kconfig.modules:2 → <nRF>/Kconfig.nrf:25 → <nRF>/subsys/Kconfig:18 → <nRF>/subsys/net/Kconfig:8 → <nRF>/subsys/net/lib/Kconfig:9

Menu path: (Top) → Modules → nrf (/home/runner/work/sdk-nrf/sdk-nrf/ncs/nrf) → Nordic nRF Connect → Networking → Application protocols → Download client

choice
    bool "HTTP(S) fragment size"
    default DOWNLOAD_CLIENT_HTTP_FRAG_SIZE_2048
    depends on DOWNLOAD_CLIENT
    help
      Size of the data fragments reported to the application when
      using HTTP or HTTPS. Use the largest fragment size when using HTTPS
      to reduce the bandwidth overhead due to the HTTP headers, which are
      sent for each fragment. When using the Modem library and TLS,
      the fragment size may not exceed 2 kB minus the largest HTTP header
      the application expects to receive.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)