diff options
author | Daiki Ueno <dueno@redhat.com> | 2018-11-24 16:59:12 +0100 |
---|---|---|
committer | Daiki Ueno <dueno@redhat.com> | 2018-11-26 06:20:39 +0100 |
commit | 401e2b97160fbed73ad72e081f9a5846423f1f14 (patch) | |
tree | d13705f315a8241c85f68c1ea4dfa865c006b599 /doc/cha-gtls-app.texi | |
parent | 712885c06b366f07d1532c1eb61e0aee6ba75f95 (diff) | |
download | gnutls-401e2b97160fbed73ad72e081f9a5846423f1f14.tar.gz |
doc: suggest to check max_early_data_size before sending early data
Signed-off-by: Daiki Ueno <dueno@redhat.com>
Diffstat (limited to 'doc/cha-gtls-app.texi')
-rw-r--r-- | doc/cha-gtls-app.texi | 16 |
1 files changed, 11 insertions, 5 deletions
diff --git a/doc/cha-gtls-app.texi b/doc/cha-gtls-app.texi index da21995cb7..5d72707dfa 100644 --- a/doc/cha-gtls-app.texi +++ b/doc/cha-gtls-app.texi @@ -949,11 +949,17 @@ 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. +When sending early data, the client should respect the maximum amount +of early data, which may have been previously advertised by the +server. It can be checked using +@funcref{gnutls_record_get_max_early_data_size}, right 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 |