Lines Matching full:retry

105 the application has to do, it must also be prepared to come back and retry the
108 such that it might succeed on the retry attempt, but this does not have to be
109 the case. It can retry at any time.
111 Note that it is important that you retry exactly the same operation that you
115 write some other text when you retry the operation.
182 to the \fBSSL\fR object and we get a "retry" response (\fBSSL_ERROR_WANT_READ\fR or
184 read or write to the underlying socket and the socket signalled the "retry".
185 With QUIC that is not the case. OpenSSL may signal retry as a result of an
188 socket needs to retry or not.
316 the event of a non-fatal failure, it waits until a retry of the I/O operation
370 messages. In such a case we must retry the same \fBSSL_connect\fR\|(3) call at a
377 \&            continue; /* Retry */
379 \&        goto end; /* Cannot retry: error */
392 that case we should retry exactly the same \fBSSL_write_ex\fR\|(3) call again. Note
395 data on a retry. An optional mode does exist
397 the buffer being written to change from one retry to the next. However, in this
398 case, you must still retry exactly the same data \- even though the buffer that
413 \&            continue; /* Retry */
415 \&        goto end; /* Cannot retry: error */
419 \&            continue; /* Retry */
421 \&        goto end; /* Cannot retry: error */
426 \&            continue; /* Retry */
428 \&        goto end; /* Cannot retry: error */
446 \&                continue; /* Retry */
453 \&                goto end; /* Cannot retry: error */
491 have to retry this operation several times. If \fBSSL_shutdown\fR\|(3) returns a
503 \&            continue; /* Retry */