Blame doc/functions/gnutls_record_set_max_size
|
Packit Service |
4684c1 |
|
|
Packit Service |
4684c1 |
|
|
Packit Service |
4684c1 |
|
|
Packit Service |
4684c1 |
|
|
Packit Service |
4684c1 |
@deftypefun {ssize_t} {gnutls_record_set_max_size} (gnutls_session_t @var{session}, size_t @var{size})
|
|
Packit Service |
4684c1 |
@var{session}: is a @code{gnutls_session_t} type.
|
|
Packit Service |
4684c1 |
|
|
Packit Service |
4684c1 |
@var{size}: is the new size
|
|
Packit Service |
4684c1 |
|
|
Packit Service |
4684c1 |
This function sets the maximum amount of plaintext sent and
|
|
Packit Service |
4684c1 |
received in a record in this connection.
|
|
Packit Service |
4684c1 |
|
|
Packit Service |
4684c1 |
Prior to 3.6.4, this function was implemented using a TLS extension
|
|
Packit Service |
4684c1 |
called 'max fragment length', which limits the acceptable values to
|
|
Packit Service |
4684c1 |
512(=2^9), 1024(=2^10), 2048(=2^11) and 4096(=2^12).
|
|
Packit Service |
4684c1 |
|
|
Packit Service |
4684c1 |
Since 3.6.4, the limit is also negotiated through a new TLS
|
|
Packit Service |
4684c1 |
extension called 'record size limit', which doesn't have the
|
|
Packit Service |
4684c1 |
limitation, as long as the value ranges between 512 and 16384.
|
|
Packit Service |
4684c1 |
Note that while the 'record size limit' extension is preferred, not
|
|
Packit Service |
4684c1 |
all TLS implementations use or even understand the extension.
|
|
Packit Service |
4684c1 |
|
|
Packit Service |
4684c1 |
@strong{Deprecated:} if the client can assume that the 'record size limit'
|
|
Packit Service |
4684c1 |
extension is supported by the server, we recommend using
|
|
Packit Service |
4684c1 |
@code{gnutls_record_set_max_recv_size()} instead.
|
|
Packit Service |
4684c1 |
|
|
Packit Service |
4684c1 |
@strong{Returns:} On success, @code{GNUTLS_E_SUCCESS} (0) is returned,
|
|
Packit Service |
4684c1 |
otherwise a negative error code is returned.
|
|
Packit Service |
4684c1 |
@end deftypefun
|