the http call always aborted after connecttimeout

Could you submit PR to fix that?

I don't get it. It sounds OK. Connect timeout for connection timeout, and read for read.

@yoavst: if the connection timeout is for example 5000 and read timeout 60000

the operation abort after 5000ms though if connection is good

this is an error because the operation should be aborted (if connection enstabilished) after readTimeout (60000ms) and not 5000ms

@carmas123: which operation?

connectionTimeout

is used while connecting,

readTimeout

is for reading when the connection is established.

oh yes I know

but try it with 1.2.1 version

and use a small connetion timeout

and a large readtimeout

probably there should be exact numbers specified simple smile as well as a network/webservice configuration you used to reproduce the issue

Well so isn't it a bug in URL connection class?

Hi, does anyone know how to disable SSL certification in fuel?

socketFactory

in

FuelManager

is configurable. Can you try to null it out?

@kittinunf: Is it possible to set

socketFactory

to null? It’s a non-nullable property

Oh my bad ….

Yeah, you are right. I dunno what I was thinking.

@asofian: You should construct SSLContext that accept all certs. Then, pass it in into

FuelManager

@rohith has left the channel

@kittinunf: I tried that out, but I'm still getting a handshake error with the request I'm trying to make. Any idea as to why this might be?

Hmm, can you share what are you currently having now?

var sc: SSLContext = SSLContext.getInstance("SSL") sc.init(null, arrayOf(TrustAllX509TrustManager()), java.security.SecureRandom()) FuelManager.instance.socketFactory = sc.socketFactory

class TrustAllX509TrustManager : X509TrustManager { override fun getAcceptedIssuers(): Array<X509Certificate>? { return null } override fun checkClientTrusted(p0: Array<X509Certificate>?, p1: String?) {} override fun checkServerTrusted(p0: Array<X509Certificate>?, p1: String?) {} }

can you try

sc.init(null, arrayOf(TrustAllX509TrustManager()), null);

?

That didn't seem to do anything 😕

Can you try with answers in this SO? http://stackoverflow.com/questions/2642777/trusting-all-certificates-using-httpclient-over-https

@kittinunf: Finally got it working using your first suggestion of setting the

setFactory

to a new value that accepts all certs in addition to modifying the

hostnameVerifier

variable to return true for all hostnames and using the

authenticate(username, password)

function. Thanks for the help!

@asofian: Glad that you made it.