Add an SSL_has_pending() function
This is similar to SSL_pending() but just returns a 1 if there is data pending in the internal OpenSSL buffers or 0 otherwise (as opposed to SSL_pending() which returns the number of bytes available). Unlike SSL_pending() this will work even if "read_ahead" is set (which is the case if you are using read pipelining, or if you are doing DTLS). A 1 return value means that we have unprocessed data. It does *not* necessarily indicate that there will be application data returned from a call to SSL_read(). The unprocessed data may not be application data or there could be errors when we attempt to parse the records. Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Emilia Käsper <emilia@openssl.org> Reviewed-by: Rich Salz <rsalz@openssl.org>
This commit is contained in:
parent
096665b0dc
commit
892b9376b3
1 changed files with 0 additions and 5 deletions
|
@ -387,8 +387,3 @@ SSL_has_pending 386 1_1_0 EXIST::FUNCTION:
|
|||
SSL_CIPHER_get_auth_nid 387 1_1_0 EXIST::FUNCTION:
|
||||
SSL_CIPHER_get_kx_nid 388 1_1_0 EXIST::FUNCTION:
|
||||
SSL_CIPHER_is_aead 389 1_1_0 EXIST::FUNCTION:
|
||||
SSL_CIPHER_get_auth_nid 390 1_1_0 EXIST::FUNCTION:
|
||||
SSL_CIPHER_get_kx_nid 391 1_1_0 EXIST::FUNCTION:
|
||||
SSL_CIPHER_is_aead 392 1_1_0 EXIST::FUNCTION:
|
||||
SSL_set_default_read_buffer_len 393 1_1_0 EXIST::FUNCTION:
|
||||
SSL_CTX_set_default_read_buffer_len 394 1_1_0 EXIST::FUNCTION:
|
||||
|
|
Loading…
Reference in a new issue