4
Configurable Expiration Time for Presigned Upload Url
Source: supabase/supabase#15394 · opened by @jfischoff
The presigned upload url feature for the Storage API uses a fixed expiration time:
This is inconsistent with the presigned download urls, which expect a body that includes a configurable expiration time.
The hardcoded time makes the feature unusable if you application cannot upload the resource in 2 hours (according to the swagger api doc although code defaults to an hour fwiw).
The upload API should work like the get presigned creation apis and take in a expiration time vs being hardcoded.
This is inconsistent with the presigned download urls, which expect a body that includes a configurable expiration time.
The hardcoded time makes the feature unusable if you application cannot upload the resource in 2 hours (according to the swagger api doc although code defaults to an hour fwiw).
The upload API should work like the get presigned creation apis and take in a expiration time vs being hardcoded.
No pledges yet. Be the first to back this.
Comments
Similar requests
URL acquisition after file upload
3 votes · 0 comments
Add `signUploadObjectUrls()` for generating multiple signed upload URLs
1 vote · 0 comments
Magic Link Expiration Time for Email Logins
3 votes · 0 comments
Storage: Upload to Bucket from Url
6 votes · 0 comments
Signed upload URL for existing files in blob storage
3 votes · 0 comments
No comments yet.