1=pod
2
3=head1 NAME
4
5SSL_write - write bytes to a TLS/SSL connection.
6
7=head1 SYNOPSIS
8
--- 11 unchanged lines hidden (view full) ---
20If necessary, SSL_write() will negotiate a TLS/SSL session, if
21not already explicitly performed by L<SSL_connect(3)|SSL_connect(3)> or
22L<SSL_accept(3)|SSL_accept(3)>. If the
23peer requests a re-negotiation, it will be performed transparently during
24the SSL_write() operation. The behaviour of SSL_write() depends on the
25underlying BIO.
26
27For the transparent negotiation to succeed, the B<ssl> must have been
28initialized to client or server mode. This is not the case if a generic
29method is being used (see L<SSL_CTX_new(3)|SSL_CTX_new(3)>, so that
30L<SSL_set_connect_state(3)|SSL_set_connect_state(3)> or SSL_set_accept_state()
31must be used before the first call to an L<SSL_read(3)|SSL_read(3)>
32or SSL_write() function.
33
34If the underlying BIO is B<blocking>, SSL_write() will only return, once the
35write operation has been finished or an error occurred, except when a
36renegotiation take place, in which case a SSL_ERROR_WANT_READ may occur.
37This behaviour can be controlled with the SSL_MODE_AUTO_RETRY flag of the
38L<SSL_CTX_set_mode(3)|SSL_CTX_set_mode(3)> call.
39
40If the underlying BIO is B<non-blocking>, SSL_write() will also return,
--- 34 unchanged lines hidden (view full) ---
75
76=item E<gt>0
77
78The write operation was successful, the return value is the number of
79bytes actually written to the TLS/SSL connection.
80
81=item 0
82
83The write operation was not successful. Call SSL_get_error() with the return
84value B<ret> to find out, whether an error occurred.
85
86=item E<lt>0
87
88The write operation was not successful, because either an error occurred
89or action must be taken by the calling process. Call SSL_get_error() with the
90return value B<ret> to find out the reason.
91
92=back
93
94=head1 SEE ALSO
95
96L<SSL_get_error(3)|SSL_get_error(3)>, L<SSL_read(3)|SSL_read(3)>,
97L<SSL_CTX_set_mode(3)|SSL_CTX_set_mode(3)>, L<SSL_CTX_new(3)|SSL_CTX_new(3)>,
98L<SSL_connect(3)|SSL_connect(3)>, L<SSL_accept(3)|SSL_accept(3)>
99L<SSL_set_connect_state(3)|SSL_set_connect_state(3)>,
100L<ssl(3)|ssl(3)>, L<bio(3)|bio(3)>
101
102=cut
2
3=head1 NAME
4
5SSL_write - write bytes to a TLS/SSL connection.
6
7=head1 SYNOPSIS
8
--- 11 unchanged lines hidden (view full) ---
20If necessary, SSL_write() will negotiate a TLS/SSL session, if
21not already explicitly performed by L<SSL_connect(3)|SSL_connect(3)> or
22L<SSL_accept(3)|SSL_accept(3)>. If the
23peer requests a re-negotiation, it will be performed transparently during
24the SSL_write() operation. The behaviour of SSL_write() depends on the
25underlying BIO.
26
27For the transparent negotiation to succeed, the B<ssl> must have been
28initialized to client or server mode. This is not the case if a generic
29method is being used (see L<SSL_CTX_new(3)|SSL_CTX_new(3)>, so that
30L<SSL_set_connect_state(3)|SSL_set_connect_state(3)> or SSL_set_accept_state()
31must be used before the first call to an L<SSL_read(3)|SSL_read(3)>
32or SSL_write() function.
33
34If the underlying BIO is B<blocking>, SSL_write() will only return, once the
35write operation has been finished or an error occurred, except when a
36renegotiation take place, in which case a SSL_ERROR_WANT_READ may occur.
37This behaviour can be controlled with the SSL_MODE_AUTO_RETRY flag of the
38L<SSL_CTX_set_mode(3)|SSL_CTX_set_mode(3)> call.
39
40If the underlying BIO is B<non-blocking>, SSL_write() will also return,
--- 34 unchanged lines hidden (view full) ---
75
76=item E<gt>0
77
78The write operation was successful, the return value is the number of
79bytes actually written to the TLS/SSL connection.
80
81=item 0
82
83The write operation was not successful. Call SSL_get_error() with the return
84value B<ret> to find out, whether an error occurred.
85
86=item E<lt>0
87
88The write operation was not successful, because either an error occurred
89or action must be taken by the calling process. Call SSL_get_error() with the
90return value B<ret> to find out the reason.
91
92=back
93
94=head1 SEE ALSO
95
96L<SSL_get_error(3)|SSL_get_error(3)>, L<SSL_read(3)|SSL_read(3)>,
97L<SSL_CTX_set_mode(3)|SSL_CTX_set_mode(3)>, L<SSL_CTX_new(3)|SSL_CTX_new(3)>,
98L<SSL_connect(3)|SSL_connect(3)>, L<SSL_accept(3)|SSL_accept(3)>
99L<SSL_set_connect_state(3)|SSL_set_connect_state(3)>,
100L<ssl(3)|ssl(3)>, L<bio(3)|bio(3)>
101
102=cut