> You may need to implement this by creating your own in-memory bio so that
> you can peek at the incoming data to determine whether it is an HTTP
> request. Then if it's not HTTP, call SSL_accept on your bio.
I was hoping I could keep ignoring this entire bio issue, because I didn't
find it all that exciting, and because I'm not sure m2crypto (a lowlevel
Python wrapping of the OpenSSL library) supports it.
Anyway, I would really like OpenSSL to decide whether it's an SSL
connection or not (it's more general, because the underlying protocol might
change in the future). I guess I could still use my own bio that remembers
everything that goes through it, and when SSL_accept fails, access the data
there.
Doesn't OpenSSL have built-in support for it (something to call after
SSL_accept to get the data that caused the failure)? That would be the
easiest thing for me.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
