'Upload from URL' routes

[akhil-rana]

Two new routes have been added.
One for uploading image file from the given URL.
The other for checking that whether the image upload has been completed or not (is useful for large image files or less bandwidth connection)

This is used with caMicroscope #353

[birm]

Request a review or otherwise let me know when you're ready with these two PRs :)

[akhil-rana]

@birm I think they are ready.
Please review them both.

[birm]

Can we give the user the ability to set an auth header for the request? e.g. for google bucket

[akhil-rana]

I'm not sure that I understand. Can you elaborate a little.

[birm]

In short, add a url param (or something) that lets a user specify an Authorization header to the url.

This is for when a url requires a specific auth header to access. In the simple case, let's pretend we're grabbing a slide from another camicroscope instance, then it needs an auth token for that instance. (though while camic can accept it as a urlparam, some sources may not).

[birm]

That said, if you don't want to do this now, that's fine; this is an improvement even without that functionality.

[akhil-rana]

Maybe workflow for the authorization header will be different for every service like google and any other. If it's alright then lets keep this option to deal with the links which directly(publicly) points to the file for now.

[akhil-rana]

However, just a thought;
maybe we can work on something like "upload from google drive" in future.
But I think it will require an API key from google. Maybe we can let the user set his/her own credentials.json file.

[birm]

I'm getting a 404 on the new route (http://localhost:4010/loader/urlupload/continue/BIYBJ2HZH3). Maybe I've messed up testing. I'll look again soon with more energy.

[akhil-rana]

url has to be passed as body in the POST request like:

{ 'url' : 'http....(encoded)' }

[akhil-rana]

Anyway even if url is not passed, 404 should not occur.🤔
Works for me perfectly. If you encounter something again. Do let me know.

[birm]

Silly me, I'd built the loader against the wrong pull request... Seems to work fine! Thanks for working through this!