Lines Matching +full:write +full:- +full:data

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
23 efficient zero-copy semantics. SSL_sendfile() is available only when
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
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
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
55 of the write function. The action depends on the underlying BIO. When using a
57 for the required condition. When using a buffering BIO, like a BIO pair, data
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)>
74 The data that was passed might have been partially processed.
76 the pointer can be different, but the data and length should still be the same.
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,
86 if SSL_MODE_ENABLE_PARTIAL_WRITE is in use, at least 1 application data byte has
91 network write buffer has temporarily filled up) or non-retryable (e.g. a fatal
101 The write operation was successful, the return value is the number of
106 The write operation was not successful, because either the connection was
110 Old documentation indicated a difference between 0 and -1, and that -1 was
122 The write operation was successful, the return value is the number
124 value can be less than B<size> for a partial write.
128 The write operation was not successful, because either the connection was
149 Copyright 2000-2021 The OpenSSL Project Authors. All Rights Reserved.