When the CONNECT request fails with a non-200 response, Excon still attempts the SSL handshake which is doomed to fail. Because of this, we end up getting a misleading SSL error rather than the actual CONNECT failure. Could we raise an error here if the proxy connection fails?

When I dug through the commit history, there was a commit that used to do this, but got removed.