In testing the beta5 release, I've noticed an apparent regression in the
async client. I have integration tests that exercise the code path where
TLS hostname verification fails (such as due to the use of a self-signed
certificate). On beta5, these tests hang forever, because the
`SSLPeerUnverifiedException` (thrown by `DefaultHostnameVerifier`) doesn't
seem to result an appropriate callback to fail the request, although it
does result in a TCP RST being sent. When I get in to work tomorrow I'm
going to investigate this further, but I wanted to highlight this bug for
the list in case anyone happens to know where specifically the regression
might have occurred.
