Lines Matching refs:SSL_write
359 /* SSL_write writes up to |num| bytes from |buf| into |ssl|. It implicitly runs
364 * In TLS, a non-blocking |SSL_write| differs from non-blocking |write| in that
365 * a failed |SSL_write
372 * By default, in TLS, |SSL_write| will not return success until all |num| bytes
374 * allows |SSL_write| to complete with a partial result when only part of the
379 * different buffer freely. A single call to |SSL_write| only ever writes a
385 OPENSSL_EXPORT int SSL_write(SSL *ssl, const void *buf, int num);
671 /* SSL_MODE_ENABLE_PARTIAL_WRITE, in TLS, allows |SSL_write| to complete with a
677 * |SSL_write| with a different buffer. However, |SSL_write| still assumes the
679 * misconception that non-blocking |SSL_write| behaves like non-blocking
694 * handshake has completely finished. |SSL_write| will function at this point,
1419 * False Start. |SSL_write| may be called at this point without waiting for the
2848 * soon as the ClientHello is processed and server flight sent. |SSL_write| may
2857 * available via the usual APIs. |SSL_write| will write early data, up to the
2863 * |SSL_write| will then act as in a 1-RTT handshake. The peer certificate and
2867 * |SSL_write|) will then fail with |SSL_get_error| returning
2892 * progressed enough to send or receive early data. Clients may call |SSL_write|
2895 * and |SSL_write| to send half-RTT data. */
2903 * 0-RTT state is discarded, including any pending |SSL_write| calls. The caller
2977 * called, future calls to |SSL_write| will fail.
