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

1 .\" -*- mode: troff; coding: utf-8 -*-
58 .TH SSL_WRITE 3ossl 2025-07-01 3.5.1 OpenSSL
64 SSL_write_ex2, SSL_write_ex, SSL_write, SSL_sendfile, SSL_WRITE_FLAG_CONCLUDE \-
65 write bytes to a TLS/SSL connection
82 \&\fBSSL_write_ex()\fR and \fBSSL_write()\fR write \fBnum\fR bytes from the buffer \fBbuf\fR into
92 efficient zero-copy semantics. \fBSSL_sendfile()\fR is available only when
107 data passed to the call is written (meaning that \f(CW\*(C`*written == num\*(C'\fR), the
115 it enables the written stream data and the FIN flag indicating the end of the
119 of the data passed to the call was consumed.
127 In the paragraphs below a "write function" is defined as one of either
130 If necessary, a write function will negotiate a TLS/SSL session, if not already
132 requests a re-negotiation, it will be performed transparently during
133 the write function operation. The behaviour of the write functions depends on the
139 before the first call to a write function.
141 If the underlying BIO is \fBblocking\fR, the write functions will only return, once
142 the write operation has been finished or an error occurred.
144 If the underlying BIO is \fBnonblocking\fR the write functions will also return
147 return value of the write function will yield \fBSSL_ERROR_WANT_READ\fR
148 or \fBSSL_ERROR_WANT_WRITE\fR. As at any time a re-negotiation is possible, a
149 call to a write function can also cause read operations! The calling process
151 of the write function. The action depends on the underlying BIO. When using a
153 for the required condition. When using a buffering BIO, like a BIO pair, data
156 The write functions will only return with success when the complete contents of
159 this flag is set the write functions will also return with success when a
160 partial write has been successfully completed. In this case the write function
161 operation is considered completed. The bytes are sent and a new write call with
163 write is performed with the size of a message block, which is 16kB.
170 is called regularly. See \fBopenssl\-quic\fR\|(7) and \fBSSL_handle_events\fR\|(3) for more
174 When a write function call has to be repeated because \fBSSL_get_error\fR\|(3)
177 The data that was passed might have been partially processed.
179 the pointer can be different, but the data and length should still be the same.
182 \&\fBSSL_write_ex()\fR can be called with num=0, but will not send application data to
187 Success means that all requested application data bytes have been written to the
189 application data byte has been written to the SSL connection. Failure means that
193 retryable (e.g. the network write buffer has temporarily filled up) or
194 non-retryable (e.g. a fatal network error). In the event of a failure call
201 The write operation was successful, the return value is the number of
205 The write operation was not successful, because either the connection was
209 Old documentation indicated a difference between 0 and \-1, and that \-1 was
216 The write operation was successful, the return value is the number
218 value can be less than \fBsize\fR for a partial write.
221 The write operation was not successful, because either the connection was
238 Copyright 2000\-2024 The OpenSSL Project Authors. All Rights Reserved.