SSL_read.pod 2.6 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
16 17 18 19 20
buffer B<buf>.

=head1 NOTES

If necessary, SSL_read() will negotiate a TLS/SSL session, if
U
Ulf Möller 已提交
21
not already explicitly performed by SSL_connect() or SSL_accept(). If the
22
peer requests a re-negotiation, it will be performed transparently during
23
the SSL_read() operation. The behaviour of SSL_read() depends on the
24 25 26
underlying BIO. 

If the underlying BIO is B<blocking>, SSL_read() will only return, once the
27 28 29 30
read operation has been finished or an error occurred, except when a
renegotiation take place, in which case a SSL_ERROR_WANT_READ may occur. 
This behaviour can be controlled with the SSL_MODE_AUTO_RETRY flag of the
L<SSL_CTX_set_mode(3)|SSL_CTX_set_mode(3)> call.
31

U
Ulf Möller 已提交
32
If the underlying BIO is B<non-blocking>, SSL_read() will also return
33 34
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 已提交
35 36
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
37 38 39 40 41 42 43
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.

44
=head1 WARNING
45 46 47 48 49

When an SSL_read() operation has to be repeated because of
B<SSL_ERROR_WANT_READ> or B<SSL_ERROR_WANT_WRITE>, it must be repeated
with the same arguments.

50 51 52 53 54 55 56 57
=head1 RETURN VALUES

The following return values can occur:

=over 4

=item E<gt>0

U
Ulf Möller 已提交
58 59
The read operation was successful; the return value is the number of
bytes actually read from the TLS/SSL connection.
60 61 62

=item 0

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

67
=item E<lt>0
68

U
Ulf Möller 已提交
69
The read operation was not successful, because either an error occurred
70 71 72 73 74 75 76 77
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)>,
78
L<SSL_CTX_set_mode(3)|SSL_CTX_set_mode(3)>,
79 80 81
L<ssl(3)|ssl(3)>, L<bio(3)|bio(3)>

=cut