Don't worry about the application -- it was a thow-away proof of concept thing, already forgotten. You're probably right there are otherways to do it. I did consider stunnel briefly but there was some reason s_client fit better into the existing perl glue code I had.
Either way though s_client's behavior is wrong, because even visually you can't _find_ the connection info mixed in with the HTTP response; my post was just to follow up having found the bug to fix the problem. The note about the application was just background of how I found it. For s_client's main purpose (command line manual testing), perhaps just the BIO_flush(bio) is all that's needed. Adam On Sun, Oct 14, 2001 at 05:33:49PM +0200, Lutz Jaenicke wrote: > What do you want to achieve? OpenSSL s_client is a test and demo program. > If you want to seperate normal I/O and the connection information, the > correct solution would be to use a seperate channel for the information. > I didn't have a look into stunnel for quite some time. Maybe it is better > suited to your needs, as it is intended for application and not for testing? ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
