diff options
author | Daiki Ueno <dueno@redhat.com> | 2018-11-24 16:59:12 +0100 |
---|---|---|
committer | Daiki Ueno <dueno@redhat.com> | 2018-11-24 17:02:46 +0100 |
commit | 2a90f39f9ab8864cdb4305c8b099c1670edd110d (patch) | |
tree | 4058a861dcaa0a3cd281c9a84a551cf2599a4fb1 | |
parent | dcf533fd1ffa17327888101c1f9a573a8937bcc1 (diff) | |
download | gnutls-tmp-minor-fixes.tar.gz |
doc: suggest to check max_early_data_size before sending early datatmp-minor-fixes
Signed-off-by: Daiki Ueno <dueno@redhat.com>
-rw-r--r-- | doc/cha-gtls-app.texi | 15 |
1 files changed, 10 insertions, 5 deletions
diff --git a/doc/cha-gtls-app.texi b/doc/cha-gtls-app.texi index da21995cb7..de4e64bd73 100644 --- a/doc/cha-gtls-app.texi +++ b/doc/cha-gtls-app.texi @@ -949,11 +949,16 @@ received data with @funcref{gnutls_record_recv_early_data}. You can call the function either after the handshake is complete, or through a handshake hook (@funcref{gnutls_handshake_set_hook_function}). -On the client side, to check whether the sent early data was accepted by -the server, use @funcref{gnutls_session_get_flags} and compare the -result with @acronym{GNUTLS_SFLAGS_EARLY_DATA}. Similarly, on the -server side, the same function and flag can be used to check whether it -has actually accepted early data. +Before sending early data, the client should check the maximum amount +of early data the server may have previously advertised. It can be +checked with @funcref{gnutls_record_get_max_early_data_size}, +immediately after calling @funcref{gnutls_session_set_data}. + +After sending early data, to check whether the sent early data was +accepted by the server, use @funcref{gnutls_session_get_flags} and +compare the result with @acronym{GNUTLS_SFLAGS_EARLY_DATA}. +Similarly, on the server side, the same function and flag can be used +to check whether it has actually accepted early data. @node Anti-replay protection |