:orphan:

.. title:: CONFIG_MBEDTLS_SSL_MAX_CONTENT_LEN

.. kconfig:: CONFIG_MBEDTLS_SSL_MAX_CONTENT_LEN

CONFIG_MBEDTLS_SSL_MAX_CONTENT_LEN
##################################

*Max payload size for TLS protocol message*

*Max payload size for TLS protocol message*

Type: ``int``

Help
====

.. code-block:: none

    The TLS standards mandate max payload size of 16384 bytes. So, for
    maximum operability and for general-purpose usage, that value must
    be used. For specific usages, that value can be largely decreased.
    E.g. for DTLS, payload size is limited by UDP datagram size, and
    even for HTTPS REST API, the payload can be limited to max size of
    (REST request, REST response, server certificate(s)).
    mbedTLS uses this value separate for input and output buffers, so
    twice this value will be allocated (on mbedTLS own heap, so the
    value of MBEDTLS_HEAP_SIZE should accommodate that).

Help
====

.. code-block:: none

    The TLS standards mandate max payload size of 16384 bytes. So, for
    maximum operability and for general-purpose usage, that value must
    be used. For specific usages, that value can be largely decreased.
    E.g. for DTLS, payload size is limited by UDP datagram size, and
    even for HTTPS REST API, the payload can be limited to max size of
    (REST request, REST response, server certificate(s)).
    mbedTLS uses this value separate for input and output buffers, so
    twice this value will be allocated (on mbedTLS own heap, so the
    value of MBEDTLS_HEAP_SIZE should accommodate that).

Direct dependencies
===================

(\ :kconfig:`MBEDTLS_BUILTIN <CONFIG_MBEDTLS_BUILTIN>` && \ :kconfig:`MBEDTLS <CONFIG_MBEDTLS>`) || (\ :kconfig:`MBEDTLS_BUILTIN <CONFIG_MBEDTLS_BUILTIN>` && \ :kconfig:`MBEDTLS <CONFIG_MBEDTLS>` && 0)

*(Includes any dependencies from ifs and menus.)*

Defaults
========

- 1500
- 1500

Kconfig definitions
===================



At ``<External Modules>/mbedtls/Kconfig:64``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:33`` → ``<External Modules>/Kconfig:6`` → ``<BuildDir>/kconfig/Kconfig.modules:26``

Menu path: (Top) → Modules → mbedtls (/home/runner/work/bridle/bridle/workspace/modules/crypto/mbedtls) → mbed TLS Support

.. code-block:: kconfig

    config MBEDTLS_SSL_MAX_CONTENT_LEN
    	int "Max payload size for TLS protocol message"
    	default 1500
    	depends on MBEDTLS_BUILTIN && MBEDTLS
    	help
    	  The TLS standards mandate max payload size of 16384 bytes. So, for
    	  maximum operability and for general-purpose usage, that value must
    	  be used. For specific usages, that value can be largely decreased.
    	  E.g. for DTLS, payload size is limited by UDP datagram size, and
    	  even for HTTPS REST API, the payload can be limited to max size of
    	  (REST request, REST response, server certificate(s)).
    	  mbedTLS uses this value separate for input and output buffers, so
    	  twice this value will be allocated (on mbedTLS own heap, so the
    	  value of MBEDTLS_HEAP_SIZE should accommodate that).

----

At ``<External Modules>/mbedtls/Kconfig:64``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:33`` → ``<External Modules>/Kconfig:74``

Menu path: (Top) → Modules → mbed TLS Support

.. code-block:: kconfig

    config MBEDTLS_SSL_MAX_CONTENT_LEN
    	int "Max payload size for TLS protocol message"
    	default 1500
    	depends on MBEDTLS_BUILTIN && MBEDTLS && 0
    	help
    	  The TLS standards mandate max payload size of 16384 bytes. So, for
    	  maximum operability and for general-purpose usage, that value must
    	  be used. For specific usages, that value can be largely decreased.
    	  E.g. for DTLS, payload size is limited by UDP datagram size, and
    	  even for HTTPS REST API, the payload can be limited to max size of
    	  (REST request, REST response, server certificate(s)).
    	  mbedTLS uses this value separate for input and output buffers, so
    	  twice this value will be allocated (on mbedTLS own heap, so the
    	  value of MBEDTLS_HEAP_SIZE should accommodate that).

*(The 'depends on' condition includes propagated dependencies from ifs and menus.)*