You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No authorization information was provided in the request - so it is certainly correct that the file is not returned. However, the appropriate DRS response in that case would likely be
403 | The requester is not authorized to perform this action.
It's not possible to tell whether the "no record found" error is masking the real issue (authorization) or whether the object is genuinely not found.
The text was updated successfully, but these errors were encountered:
The following DRS call returns two access methods for the specified file
https://dataguids.org/ga4gh/drs/v1/objects/3ed3640c-8a82-4ec0-9d3e-2cd9b5a62707
See attached file for response
3ed3640c-8a82-4ec0-9d3e-2cd9b5a62707.txt
Given that response it should be possible to obtain a URL for the file via either of the following calls
https://dataguids.org/ga4gh/drs/v1/objects/3ed3640c-8a82-4ec0-9d3e-2cd9b5a62707/access/s3
https://dataguids.org/ga4gh/drs/v1/objects/3ed3640c-8a82-4ec0-9d3e-2cd9b5a62707/access/gs
Both return
{
"error": "no record found"
}
No authorization information was provided in the request - so it is certainly correct that the file is not returned. However, the appropriate DRS response in that case would likely be
403 | The requester is not authorized to perform this action.
It's not possible to tell whether the "no record found" error is masking the real issue (authorization) or whether the object is genuinely not found.
The text was updated successfully, but these errors were encountered: