I'm running into all sorts of filter problems. The initial client request is itself not received completely.. For ex., the apr_bucket_read (ssl_engine_io.c:218) returns 20 bytes when the client has sent 103 bytes.
The ssl_hook_process_connection (mod_ssl.c:360) returns with a error to read more (which is not being handled right now). This is a problem as the SSL filter expects that *all* the data sent by the client is received in one complete chunk.. If I try forcing the bucket_read again (incase of a SSL_WANT_READ error), it's still not able to read the full data. Any ideas.. **** PSEUDO LOG *** apr_bucket_read : returned 20 bytes OpenSSL: write 20/20 bytes to BIO#40127010[mem: 40129100] ... OpenSSL: read 11/11 bytes from BIO#40127010[mem: 40130868] .... OpenSSL: read 9/103 bytes from BIO#40127010[mem: 40130873] ... OpenSSL: I/O error, 94 bytes expected to read on BIO#40127010 [mem: 4013087C] OpenSSL: Exit: error in SSLv2/v3 read client hello B **** END PSEUDO LOG *** Thx -Madhu -----Original Message----- From: William A. Rowe, Jr. To: [EMAIL PROTECTED] Sent: 10/2/01 6:34 PM Subject: Re: ssl is broken From: "Justin Erenkrantz" <[EMAIL PROTECTED]> Sent: Tuesday, October 02, 2001 8:29 PM > On Tue, Oct 02, 2001 at 01:24:25PM -0700, Doug MacEachern wrote: > > with current cvs all httpd-test ssl tests hang, stacktrace is same for > > all... > > I bet it's related to the input filtering changes. > > I have no clue how the whole mod_ssl input filtering works, but I'll > try to take a look. My guess is that mod_ssl is just a big quagmire. That, or your input filtering changes were the big quagmire. Either way, that sure sounds like the interaction that broke ssl.
