Error with Permissions-Policy header: Unrecognized feature: 'interest-cohort'. ?

[yarikoptic]

what could be a reason?

continuation to dandi/dandi-infrastructure#88 to make
https://bioimagesuiteweb.github.io/webapp/viewer.html?image=https://api.dandiarchive.org/api/assets/d62f3ac5-2a0f-4170-a2d9-37d9bb2085c0/download/ (which redirects to a pre-signed S3 URL) work.

access from datasets.datalad.org works fine on another image: https://bioimagesuiteweb.github.io/webapp/viewer.html?image=https://datasets-dev.datalad.org/dbic/QA/sub-emmet/ses-20180508/anat/sub-emmet_ses-20180508_acq-MPRAGE_T1w.nii.gz but when trying to get the asset from api download url -- getting that error logged in the console.

The same error with a direct url to S3 (not presigned, to get content-disposition):
https://bioimagesuiteweb.github.io/webapp/viewer.html?image=https://dandiarchive.s3.amazonaws.com/blobs/a62/0e5/a620e50a-22e9-4694-8ac5-5b784df07ccd so I guess it is not dandi-api issue, thus inquiring here.

Search for it +S3 gives no immediate hits, thus inquiring here for ideas.

[XeniosP]

Let me take a look when I am back to the office. My hunch is that this is a configuration problem on the server side.

[yarikoptic]

Just a gentle ping (unless still far from the office ;))

[XeniosP]

We need to debug this together.

[EnkhAmar]

Hi, How did you resolve this issue?

[bioimagesuiteweb]

There is a fix on the unstableapp branch i.e. https://bioimagesuiteweb.github.io/webapp/unstableapp/viewer.html ...

It was mostly an issue on Bisweb looking for a suffix on the filename -- we changed the default behavior to assume NIFTI-1 if there was none (unless my memory fails me).