SSL_read.pod 2.2 KB
Newer Older
1 2 3 4
=pod

=head1 NAME

U
Ulf Möller 已提交
5
SSL_read - read bytes from a TLS/SSL connection.
6 7 8 9 10 11 12 13 14 15

=head1 SYNOPSIS

 #include <openssl/ssl.h>

 int SSL_read(SSL *ssl, char *buf, int num);

=head1 DESCRIPTION

SSL_read() tries to read B<num> bytes from the specified B<ssl> into the
U
Ulf Möller 已提交
16 17
buffer B<buf>. If necessary, SSL_read() will negotiate a TLS/SSL session, if
not already explicitly performed by SSL_connect() or SSL_accept(). If the
18
peer requests a re-negotiation, it will be performed transparently during
19
the SSL_read() operation. The behaviour of SSL_read() depends on the
20 21 22
underlying BIO. 

If the underlying BIO is B<blocking>, SSL_read() will only return, once the
U
Ulf Möller 已提交
23
read operation has been finished or an error occurred.
24

U
Ulf Möller 已提交
25
If the underlying BIO is B<non-blocking>, SSL_read() will also return
26 27
when the underlying BIO could not satisfy the needs of SSL_read()
to continue the operation. In this case a call to SSL_get_error() with the
U
Ulf Möller 已提交
28 29
return value of SSL_read() will yield B<SSL_ERROR_WANT_READ> or
B<SSL_ERROR_WANT_WRITE>. As at any time a re-negotiation is possible, a
30 31 32 33 34 35 36 37 38 39 40 41 42 43 44
call to SSL_read() can also cause write operations! The calling process
then must repeat the call after taking appropriate action to satisfy the
needs of SSL_read(). The action depends on the underlying BIO. When using a
non-blocking socket, nothing is to be done, but select() can be used to check
for the required condition. When using a buffering BIO, like a BIO pair, data
must be written into or retrieved out of the BIO before being able to continue.

=head1 RETURN VALUES

The following return values can occur:

=over 4

=item E<gt>0

U
Ulf Möller 已提交
45 46
The read operation was successful; the return value is the number of
bytes actually read from the TLS/SSL connection.
47 48 49

=item 0

U
Ulf Möller 已提交
50
The read operation was not successful, probably because no data was
51
available. Call SSL_get_error() with the return value B<ret> to find out,
U
Ulf Möller 已提交
52
whether an error occurred.
53 54 55

=item -1

U
Ulf Möller 已提交
56
The read operation was not successful, because either an error occurred
57 58 59 60 61 62 63 64 65 66 67
or action must be taken by the calling process. Call SSL_get_error() with the
return value B<ret> to find out the reason.

=back

=head1 SEE ALSO

L<SSL_get_error(3)|SSL_get_error(3)>, L<SSL_write(3)|SSL_write(3)>,
L<ssl(3)|ssl(3)>, L<bio(3)|bio(3)>

=cut