Unable to read files behind pre-signed S3 URLs
See original GitHub issueI’ve been using CERN S3 to redirect to pre-signed S3 URLs to avoid needing to proxy potentially large files. These files however are not readable with JSROOT as it’s not possible to sign a URL for both HEAD and GET requests.
I think the only issue is this bit of code that tries to set fAcceptRanges
, would it be possible to either tollerate the request failing or, as it’s a widely used standard, detect if the URL has the S3 signing parameters.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Using presigned URLs - Amazon Simple Storage Service
Use a presigned URL to share or upload objects in Amazon S3 without requiring AWS security credentials or permissions.
Read more >Can't access S3 Pre-Signed URL due to authorization [duplicate]
Using Java8 and aws-java-sdk 1.10.43 I'm trying to get a Pre-Signed URL to an S3 file. I do get back a link, but...
Read more >Securing your Amazon AWS S3 presigned URLs, tips and tricks
When your service returns a presigned URL to a user, the user will consume it to read / upload an object directly from...
Read more >S3: Support for multipart upload using presigned url #1603
An update as I've learned a lot more about the strategy to upload files direct from browser to S3 bucket using multipart and...
Read more >AWS S3 uploads using pre-signed URLs - ABHISHEK KUMAR
Anyone with a valid pre-signed URL can interact with the objects as specified during creation. For example, if a GET (Read) pre-signed URL...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I add another workaround with
^
at the end of the file name. It just skip 'HEAD` request, which normally used to get some basic server and file attributes. Available in master branch - would be nice if you can test itThanks @linev for the incredibly fast solution!