mbedtls_ssl_conf_max_frag_len() is only used within mbedTLS.
 
Symbols
loading...
Files
loading...
SummarySyntaxArgumentsRelatedReferencesCall TreeData Use

Return value

0 if successful or MBEDTLS_ERR_SSL_BAD_INPUT_DATA

Notes

On the client side, the maximum fragment length extension *will not* be used, unless the maximum fragment length has been set via this function to a value different than #MBEDTLS_SSL_MAX_FRAG_LEN_NONE. With TLS, this currently only affects ApplicationData (sent with \c mbedtls_ssl_read()), not handshake messages. With DTLS, this affects both ApplicationData and handshake. This sets the maximum length for a record's payload, excluding record overhead that will be added to it, see \c mbedtls_ssl_get_record_expansion(). For DTLS, it is also possible to set a limit for the total size of datagrams passed to the transport layer, including record overhead, see \c mbedtls_ssl_set_mtu().

References