Lines Matching full:retry

55 the application has to do, it must also be prepared to come back and retry the
58 such that it might succeed on the retry attempt, but this does not have to be
59 the case. It can retry at any time.
61 Note that it is important that you retry exactly the same operation that you
65 write some other text when you retry the operation.
130 to the B<SSL> object and we get a "retry" response (B<SSL_ERROR_WANT_READ> or
132 read or write to the underlying socket and the socket signalled the "retry".
133 With QUIC that is not the case. OpenSSL may signal retry as a result of an
136 socket needs to retry or not.
263 the event of a non-fatal failure, it waits until a retry of the I/O operation
315 messages. In such a case we must retry the same L<SSL_connect(3)> call at a
321             continue; /* Retry */
323         goto end; /* Cannot retry: error */
336 that case we should retry exactly the same L<SSL_write_ex(3)> call again. Note
339 data on a retry. An optional mode does exist
341 the buffer being written to change from one retry to the next. However, in this
342 case, you must still retry exactly the same data - even though the buffer that
356             continue; /* Retry */
358         goto end; /* Cannot retry: error */
362             continue; /* Retry */
364         goto end; /* Cannot retry: error */
369             continue; /* Retry */
371         goto end; /* Cannot retry: error */
387                 continue; /* Retry */
394                 goto end; /* Cannot retry: error */
432 have to retry this operation several times. If L<SSL_shutdown(3)> returns a
443             continue; /* Retry */