Ok, I've got a fix.
The issue is that we use a debug callback to track the bytes read/written. This callback is called with a kind and a text.
Some curl implementations calls our callback for INFOTYPE_SSL_DATA_OUT and INFOTYPE_SSL_DATA_IN (i.e. the encrypted text), some don't.
The bug is that we should never take these kinds into account anyway but until I could reproduce the issue I didn't realize that.
Thanks for your reproducing instructions !!
Ok, I've got a fix.
The issue is that we use a debug callback to track the bytes read/written. This callback is called with a kind and a text.
Some curl implementations calls our callback for INFOTYPE_ SSL_DATA_ OUT and INFOTYPE_ SSL_DATA_ IN (i.e. the encrypted text), some don't.
The bug is that we should never take these kinds into account anyway but until I could reproduce the issue I didn't realize that.
Thanks for your reproducing instructions !!