I'm using openssl-0.9.7d in a multithreaded application and want to do some
special processing in the case of a client mistakenly trying to connect without
SSL to a port which is expecting SSL (i.e. someone types "http://foo.com:10000";
into their browser instead of "https://foo.com:10000";). Looking at s23_srvr.c
there is even an error code for this called SSL_R_HTTP_REQUEST. The
complication is that my application uses a "worker thread" model for handling
connections, there is not one thread per SSL connection. Therefore the error
stack, which is stored per thread, doesn't really help me since I don't know
which connection the error information applies to since a given thread may do
work for multiple connections. Does anyone know if there is another way to get
error information which is per connection and not tied to the thread? I
haven't found anything in the SSL or SSL_CTX objects which seem right.
I've also tried hooking into the info_callback and msg_callback callbacks, but
neither provides any information in this case of an error right from the get
go.
Thanks very much,
-- Jonathan
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
