DO NOT REPLY [Bug 8165] New: - weird: 100% cpu usage after a simple single ssl connection

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8165>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8165

weird: 100% cpu usage after a simple single ssl connection

           Summary: weird: 100% cpu usage after a simple single ssl
                    connection
           Product: Apache httpd-2.0
           Version: 2.0.35
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: mod_ssl
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: andreas@netbank.com.br


This is weird. apache-2.0.35 compiled with ssl and --with-mpm=worker on linux.
Starting it with ssl works fine, both port 80 and 443 are open and serving
requests. The funny thing is that if I make a https:// request with lynx,
everything works just fine, the page is served via SSL. But if I make the same
request with curl (curl https://localhost, it just sends back my small
index.html file), httpd goes up to 100% cpu usage, even *after* the request has
been served. That is, there are no more established connections to the web
server. BTW, curl downloads and displays the index.html file without problems,
just the server gets really slow after this single connection.
I'm using a self-signed certificate.
Mozilla doesn't prompt this behaviour in the web server. This is weird, I hope
I'm doing something wrong.
I also tried curl and lynx from another machine (not localhost), and it happened
again.