PreSignedUrl resource caching #2493
-
It's obvious that PreSignedUrls cannot be cached. Is there a way to give to the client Authorization header value for a file in S3 that would enable using a direct url to secured file with auth set in headers? We store images in S3 and we cannot make them public. The only way is download each time in the server and return back a blob or use presigned urls. None of these approaches will enable caching. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
@MursalovAltun I'm unaware about any such possibility. The private objects can be shared using presigned URLs which expire within configured time frame. So I could understand why it wouldn't support caching. |
Beta Was this translation helpful? Give feedback.
-
Hello! Reopening this discussion to make it searchable. |
Beta Was this translation helpful? Give feedback.
@MursalovAltun I'm unaware about any such possibility. The private objects can be shared using presigned URLs which expire within configured time frame. So I could understand why it wouldn't support caching.