On 03/13/2013 03:25 PM, Mark Thomas wrote:
On 13/03/2013 14:07, Mladen Turk wrote:
00000026 7.85627747 [3976] SSL_write returned -1,
apr_get_netos_error=0 SSL_get_error=1
That's a problem
apr_get_netos_error returned zero (and thats what we return)
However SSL_get_error returned SSL_ERROR_SSL (1) and we don't handle that!
Sending you a version that returns APR_EGENERAL on SLL_ERROR_SSL ...
Thanks. That fails fast which is good but still fails. Fundamentally we
need to be able to handle the situation when we have some, but not
enough data for OpenSSL.
Sure. I just returned APR_EGENERAL. Some dedicated retval would be
required so that Java part figures out more data is needed.
Are there any error descriptions in dbgview window?
On a possibly related topic...
I've noticed that the non-blocking writes via APR/native doesn't behave
as I would expect. Consider the output from the test case [1]
SSL_write is weird. Docs says that if the return value is EAGAIN the
next SSL_write *must* be called with the same params. I presume it internally
maintains a state logic or something.
Regards
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
