How to handle download automatically in webview

[delight-im]

How to handle download automatically in webview

[ocram]

Thanks for your question!

You understood everything correctly and put this method in the right place. The only problem you have is the missing filename, right?

Well, that's easier than you might have thought:

Actually, you could just hard-code a filename into that method, which would look like this:

final String filename = "my-file.txt;

But this would always download and save any file under the name my-file.txt. That's probably not what you want, right?

But you can do everything you want with this filename. For example, you could add the current timestamp at the beginning of that name so that files have unique names:

final String filename = System.currentTimeMillis()+" my-file.txt";

Alternatively, you could include your app's name, etc.

But another important thing that you'd probably want to change is the file extension. If you know what extension the file must have, that's great, then you can hard-code it as in the examples above. But often, it won't always be a text file, so you could detect the file extension from the MIME type that is passed as a method parameter:

final String filename;
if (mimetype.equals("image/jpeg")) {
    filename = "my-photo.jpg";
}
else if (mimetype.equals("text/html")) {
    filename = "my-document.html";
}
else {
    // we didn't expect this MIME type and so we don't have any reasonable extension
    filename = "my-file";
}

Hope that helps!

[Shirishasai]

Thanks for your suggestion it worked .:-)
But am unable to cancel the download once started .Can you please help on it.

[ocram]

Glad that it worked :)

Cancelling any download is not currently possible when you let this library handle the downloads automatically. This would be possible in the future, but it will require some small changes to the source code:

Here and here, DownloadManager#enqueue() is called, which returns a unique ID for each download. Those IDs would have to be stored and be passed to DownloadManager#remove() when a future method (potentially named stopDownloads() or something like this) would be called.

Is this really important? From what we know, cancelling downloads is only rarely needed.