httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 49382] New: ab says "SSL read failed"
Date Thu, 03 Jun 2010 20:27:14 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=49382

           Summary: ab says "SSL read failed"
           Product: Apache httpd-2
           Version: 2.2.15
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: support
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: peak@argo.troja.mff.cuni.cz


ab has trouble receiving responses from many HTTPS non-Apache servers (IIS 6.0,
Lotus Domino, Google gws), complaining that "SSL read failed":

$ ./ab https://www.google.com/
...
This is ApacheBench, Version 2.3 <$Revision: 655654 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking www.google.com (be patient)...SSL read failed - closing connection
..done

Those servers seem to terminate TCP connection after the response without
shutting down SSL session properly (using close_notify).

A possible workaround is to stop reading after Content-Length bytes have been
received. I have implemented that that workaround (see the attachment). It
appears to work in most cases, the only notable exception is Google gws because
it does not send Content-Length in responses to HTTP/1.0 request.

Trunk (2.3) appears to be affected too.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message