When the server does not offer the option of 'resuming', the API should 'restart' the download automatically or deliver an error, and exposing a 'restart' method.

Fabrice, when testing the API I've discovered this issue, could you take a look? Thanks!!

Please cc Aus to any download bugs, as he's taking over the platform part.

Hi Aus, When testing I've realized that this feature is broken, and we would need to have at least the basic functionality ready within our 1.3 goal. Could you help us on this? Thanks!

Yep, I'll take a look. The tests should have caught this...

Borja, could you re-test this please? This functions as expected for me. I've re-written the test for resuming and it passes as expected and the download does resume. One key thing to remember is that the Promise returned when calling resume() will only get called when the resumed download FINISHES. There is a status change event though that will show the download going from stopped to downloading. I'll be landing the new tests as part of this bug to ensure that everything keeps on working. If this does not work for you, please let me know how you are testing it. Resuming typically requires http 1.1 and support for range requests. If those aren't available, resuming will fail and you'll need to restart the download yourself by finalizing the failed download object and creating a new one.

This seems to be working now. Marking as WORKSFORME. Thanks!