unspent-outputs to return proper HTTP error when timing out

[schildbach]

When asking for unspent outputs it sometimes times out which doesn't return a proper HTTP error.

https://api.biteasy.com/blockchain/v1/unspent-outputs?per_page=MAX&address%5B%5D=1KSBig8uywSV1SHjGucvNQsWxDAV1qw7tz

In apps, it looks like as if SSL handshake was broken:

SSL handshake aborted:
ssl=0x7779cbf8: Failure in SSL library, usually a protocol error
error:14077410:SSL
routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure
(external/openssl/s23_clnt.c:741 0x72f7d7e8:0x00000000)

[alolis]

Hm, it shouldn't timeout in the first place. I will investigate today and get back to you.

[alolis]

Well, I fixed the timeout issue although it's a bit slow at the moment. I am still investigating but at least it does not blow up. I expected that the address had a lot of unspent outputs and that's why it timed out but I only see 1 unspent output for it.

[alolis]

@schildbach , are you still having problems with this?

[schildbach]

It doesn't time out any more. I do not know if it would return the correct http error when it would time out.

[alolis]

A timeout should never occur, if it does then it means that something serious is going on but I will try to make it to return a proper http code.

[schildbach]

Ok. Thanks for helping with this!

[schildbach]

Some users are having this issues from time to time, e.g. with this request:

https://api.biteasy.com/blockchain/v1/unspent-outputs?per_page=MAX&address[]=15VY3kQZV9d8rTvxZ6Hfu7JFoa3TJuyguQ

[alolis]

@schildbach , I never saw your post! Yeah I can understand why this is happening but v1 API is kinda deprecated and it won't be fixed. It does work in v2 though, which we are trying to put fully in production. Mainnet should be indexed with v2 soon and you will be able to make a few tests with it.