Lines Matching +full:write +full:- +full:to +full:- +full:write

5 SSL_write_ex, SSL_write, SSL_sendfile - write bytes to a TLS/SSL connection
17 SSL_write_ex() and SSL_write() write B<num> bytes from the buffer B<buf> into
22 descriptor B<fd> to the specified SSL connection B<s>. This function provides
23 efficient zero-copy semantics. SSL_sendfile() is available only when
25 It is provided here to allow users to maintain the same interface.
31 In the paragraphs below a "write function" is defined as one of either
34 If necessary, a write function will negotiate a TLS/SSL session, if not already
36 requests a re-negotiation, it will be performed transparently during
37 the write function operation. The behaviour of the write functions depends on the
40 For the transparent negotiation to succeed, the B<ssl> must have been
41 initialized to client or server mode. This is being done by calling
43 before the first call to a write function.
45 If the underlying BIO is B<blocking>, the write functions will only return, once
46 the write operation has been finished or an error occurred.
48 If the underlying BIO is B<nonblocking> the write functions will also return
49 when the underlying BIO could not satisfy the needs of the function to continue
50 the operation. In this case a call to L<SSL_get_error(3)> with the
51 return value of the write function will yield B<SSL_ERROR_WANT_READ>
52 or B<SSL_ERROR_WANT_WRITE>. As at any time a re-negotiation is possible, a
53 call to a write function can also cause read operations! The calling process
54 then must repeat the call after taking appropriate action to satisfy the needs
55 of the write function. The action depends on the underlying BIO. When using a
56 nonblocking socket, nothing is to be done, but select() can be used to check
58 must be written into or retrieved out of the BIO before being able to continue.
60 The write functions will only return with success when the complete contents of
63 this flag is set the write functions will also return with success when a
64 partial write has been successfully completed. In this case the write function
65 operation is considered completed. The bytes are sent and a new write call with
67 write is performed with the size of a message block, which is 16kB.
71 When a write function call has to be repeated because L<SSL_get_error(3)>
79 SSL_write_ex() can be called with num=0, but will not send application data to
85 all requested application data bytes have been written to the SSL connection or,
87 been written to the SSL connection. Failure means that not all the requested
89 no bytes could be written to the SSL connection (if
91 network write buffer has temporarily filled up) or non-retryable (e.g. a fatal
92 network error). In the event of a failure call L<SSL_get_error(3)> to find out
101 The write operation was successful, the return value is the number of
102 bytes actually written to the TLS/SSL connection.
106 The write operation was not successful, because either the connection was
108 Call SSL_get_error() with the return value B<ret> to find out the reason.
110 Old documentation indicated a difference between 0 and -1, and that -1 was
112 You should instead call SSL_get_error() to find out if it's retryable.
122 The write operation was successful, the return value is the number
123 of bytes of the file written to the TLS/SSL connection. The return
124 value can be less than B<size> for a partial write.
128 The write operation was not successful, because either the connection was
130 Call SSL_get_error() with the return value to find out the reason.
149 Copyright 2000-2021 The OpenSSL Project Authors. All Rights Reserved.