next "timeout" doesn't work as expected (i guess)

Nobody has claimed this yet.

Hi,

Recently in one of my project [Node-secure](https://github.com/ES-Community/nsecure) i spotted that the part of the code that was responsible to fetch data on the npm registry was not able to properly terminate (some asynchronous function never end).

This code use one of my package that is: https://github.com/SlimIO/Npm-registry. I recently updated this package with the next version of httpie in hope to fix the problem with the new **timeout** option.

But the problem is still there :\

I made a repository to reproduce the problem without all the noise: https://github.com/fraxken/httpie_timeout_bug

Sometimes it work (i guess it work when npm return 200 for every packages of the list). But sometimes it seem to never end (even with the timeout).

Best Regards,
Thomas

Start with the reproduction repository at https://github.com/fraxken/httpie_timeout_bug and inspect how the httpie timeout option behaves when npm requests do not all return 200. Trace the asynchronous request path in the httpie package and establish why the operation can remain pending; done means the reproduction terminates consistently when the timeout is reached.

Written by the indexing model from the issue text.