https://issues.apache.org/bugzilla/show_bug.cgi?id=49382
--- Comment #4 from Ian Webb <[email protected]> 2012-03-07 20:37:40 UTC --- Upon further testing, I've found some sites this still doesn't work on. In particular, I've verified that ab will now work fine with -n1 against https://www.google.com/ and https://www.facebook.com/, but will fail with -n2 or higher. The failure modes seem slightly different but both Google and Facebook "cheat" in various ways for performance (such as defeating slow-start) so I'm not too surprised this fails on those two. (Other Google properties, such as https://gmail.com/, work fine.) In testing against most sites I monitor in production it works fine. This represents a mix of Apache, IIS, nginx, and F5 BigIP HTTPS servers. I have found one Tomcat 5.5 that fails, unfortunately this may be exposing a serious error. The first request resolves with a 200, then subsequent requests seem to be continuing the data flow from that first request and interpreting it as a 500. Note that the function (this was with -v2, the failure happens in a part of the page that has JavaScript so that's just page data) is cut off in the middle by a 500 response code. Not sure what's going on. function popWindowSecure(url,winnam WARNING: Response code not 2xx (500) LOG: header received: e,width,height) -- 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: [email protected] For additional commands, e-mail: [email protected]
