diff options
| author | Nikos Mavrogiannopoulos <nmav@redhat.com> | 2016-04-15 10:14:22 +0200 |
|---|---|---|
| committer | Nikos Mavrogiannopoulos <nmav@redhat.com> | 2016-04-15 10:14:22 +0200 |
| commit | eaa8f5f24c91877b25c444a4fbddb5b5ee30f683 (patch) | |
| tree | 9ee1d6293878d6bf8112cab686acd4f860d0481b | |
| parent | 45447d974c21665fae9e546b3857aefdf83f9d06 (diff) | |
| download | gnutls-eaa8f5f24c91877b25c444a4fbddb5b5ee30f683.tar.gz | |
doc: further updated documentation on false start [ci skip]
| -rw-r--r-- | doc/cha-intro-tls.texi | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/cha-intro-tls.texi b/doc/cha-intro-tls.texi index 60c289640e..842939a628 100644 --- a/doc/cha-intro-tls.texi +++ b/doc/cha-intro-tls.texi @@ -652,6 +652,11 @@ to request an early return of the @funcref{gnutls_handshake} function. After tha return the application is expected to transfer any data to be piggybacked on the last handshake message. +After handshake's early termination, the application is expected to call +@funcref{gnutls_record_recv} on any received data as soon, to ensure that handshake +completes timely. That is, especially relevant for applications which set an explicit +time limit for the handshake process via @funcref{gnutls_handshake_set_timeout}. + Note however, that the API ensures that the early return will not happen if the false start requirements are not satisfied. That is on ciphersuites which are not whitelisted for false start (see @xcite{draft-ietf-tls-falsestart-01}), the handshake |