haskell / wreq

BSD 3-Clause "New" or "Revised" License
380 stars 71 forks source link

TlsExceptionHostPort (HandshakeFailed Error_EOF) "chrome.google.com" 443 #88

Closed akhra closed 6 years ago

akhra commented 8 years ago

Not the greatest issue title but I can't think of a more concise summary! This is happening with any request I make to chrome.google.com, and nowhere else (that I've found -- notably working sites include Steam, Amazon, iTunes). It occurs with both tlsManagerSettings and a constructed manager with TLSSettings True False False, and also with regular HTTP on port 80. It's possible this is some sort of deliberate rejection, but EOF during the handshake isn't the usual signal for that and I've dug about as far as my "expertise" reliably allows. Figured I should pass it upstream for review, at least.

The application is a product data scraper service, public source available here: https://github.com/tejon/Meeseeks

erdeszt commented 8 years ago

I'm having a similar issue, one of my application that was running fine before failed after a new build/deploy today with this message: TlsExceptionHostPort (HandshakeFailed (Error_Protocol ("certificate rejected: [SelfSigned]",True,CertificateUnknown))) "api.enterprise.apigee.com" 443 But if I open https://api.enterprise.apigee.com in chrome I get the green lock icon indicating that the connection is secure. I can provide code or can try the tls settings mentioned by @tejon if necessary.

isamert commented 7 years ago

I'm also getting this exact same error on google related pages which even includes google.com. More interestingly, I don't get this error on m.google.com.

sgronblo commented 7 years ago

I get this same error when trying to access calendar.google.com. Curl does not complain about the same URL.

filterfish commented 7 years ago

This was a problem in hs-tls. See here: https://github.com/vincenthz/hs-tls/issues/152

You should just be able to use tls-1.3.9 it in stackage lts-7.16 and nightles of course. It worked for me.

ondrap commented 6 years ago

Not a wreq problem, closing.