(some?) pre-signed S3 URLs do not work

[yarikoptic]

In follow up to prior integration with the dandiarchive.org: https://github.com/dandi/dandi-infrastructure/issues/10

With our recent migration to a new backend we changed the URLs we provide, although IIRC it should have not been in substantial way since previously the URLs also lead to redirection to pre-signed (IIRC, but I could be wrong on this) urls. ATM trying out following urls on http://nwbexplorer.opensourcebrain.org/ :

• https://api.dandiarchive.org/api/dandisets/000027/versions/draft/assets/ff453f4c-a435-4a5d-a48b-128abca5ec47/download/ - doesn't work
• its redirect https://dandiarchive.s3.amazonaws.com/blobs/2db/af0/2dbaf0fd-5003-4a0a-b4c0-bc8cdbdb3826?response-content-disposition=attachment%3B%20filename%3D%22sub-RAT123.nwb%22&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAUBRWC5GAEKH3223E%2F20210507%2Fus-east-2%2Fs3%2Faws4_request&X-Amz-Date=20210507T143923Z&X-Amz-Expires=3600&X-Amz-SignedHeaders=host&X-Amz-Signature=9eb901445e76a40c543aa1e3aae89352fed9a3d5a2557280e5f05f8b323d0c82 doesn't work
• direct simple S3 url (without content-disposition etc provided by signed url): https://dandiarchive.s3.amazonaws.com/blobs/2db/af0/2dbaf0fd-5003-4a0a-b4c0-bc8cdbdb3826 - works
• direct S3 url with versionId: http://dandiarchive.s3.amazonaws.com/blobs/2db/af0/2dbaf0fd-5003-4a0a-b4c0-bc8cdbdb3826?versionId=4BMLdtv04lfi7JDWFfUleHVzYazeFVL4 - works

Do you think it is some issue which could be addressed on nwb-explorer side or we need to figure out some workaround on our (dandi) side?

Thank you in advance

Attn @satra @pgleeson

[satra]

i would suggest supporting the api url as that's likely to stick around, internally the s3 redirect could be hashed/cached, but i leave that at the explorer level.

[yarikoptic]

@pgleeson et al ping on this.

[filippomc]

@yarikoptic yes agree it can be annoying for the user. Will implement the file loading in order to follow redirects.