> Anyway, I'm on 0.9.8e and I've got an application that's doing a lot of > BIO_write's to a server via TLS. When the write buffer is full, I get -1 > from BIO_write (as expected) and BIO_should_retry returns "do retry" (as > expected), but when I go to write again a little bit later I get > SSL_R_BAD_WRITE_RETRY. Now, the important part of this is I'm not writing > the same thing the second time... it's a different buffer, different > contents, different length. In my application, the old buffer is > stale and > the new one is more applicable so I'm not writing the same thing > again even > though the previous write never got sent. Now, > SSL_MODE_ACCEPT_MOVING_WRITE_BUFFER doesn't really help me, since > the buffer > contents and length are different. But since I'm not using > SSL_MODE_ENABLE_PARTIAL_WRITE, I'm not sure why any of this > matters anyway? > Shouldn't the behavior of the BIO_write in the mode of no partial > writes be > as if the BIO_write never happened if it fails? I'm wondering why there's > leftover state causing this error?
Just to clarify: 1) You specifically did not tell OpenSSL to accept a moving write buffer. 2) You are wondering why OpenSSL is not accepting a moving write buffer. Does that sum up your problem? DS ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [EMAIL PROTECTED]
