Help¶

Size of the data fragments reported to the application in each event when not using TLS. Use a larger fragment size to reduce the bandwidth overhead due to the HTTP headers.

Direct dependencies¶

DOWNLOAD_CLIENT

(Includes any dependencies from ifs and menus.)

Default¶

4096

Kconfig definition¶

At /jenkins_workspace/workspace/nrfconnect-nrf_doc_v1.2-branch_2/nrf/subsys/net/lib/download_client/Kconfig:12

Included via Kconfig:8 → Kconfig.zephyr:9 → /jenkins_workspace/workspace/nrfconnect-nrf_doc_v1.2-branch_2/test_doc/_build/Kconfig.modules:1 → /jenkins_workspace/workspace/nrfconnect-nrf_doc_v1.2-branch_2/nrf/Kconfig.nrf:10 → /jenkins_workspace/workspace/nrfconnect-nrf_doc_v1.2-branch_2/nrf/subsys/Kconfig:16 → /jenkins_workspace/workspace/nrfconnect-nrf_doc_v1.2-branch_2/nrf/subsys/net/Kconfig:8 → /jenkins_workspace/workspace/nrfconnect-nrf_doc_v1.2-branch_2/nrf/subsys/net/lib/Kconfig:9

Menu path: (Top) → Modules → Nordic nRF Connect → Networking → Application protocols → Download client

config DOWNLOAD_CLIENT_MAX_FRAGMENT_SIZE
    int "Non-TLS fragment size"
    range 512 4096
    default 4096
    depends on DOWNLOAD_CLIENT
    help
      Size of the data fragments reported to the application in each event
      when not using TLS. Use a larger fragment size to reduce the
      bandwidth overhead due to the HTTP headers.

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