Support S3 signed URLs for private buckets #141
Labels
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: aheathershaw/blue-twilight#141
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Provide a config setting on the S3 driver to decide whether to use a signed URL when creating links to photos.
This should be enabled by default on new storage locations using the driver, but disabled by default on existing ones.
When this option is enabled, uploaded images should use the "private" ACL, otherwise the "public-read" URL.
When this option is enabled, any URLs generated to photos should use the signed URL functionality of S3.
This is completed with one small snag - the admin actions in the control panel force a cache buster when the image has been reloaded.
This is causing the signature to be invalid when the preview image is reloaded.
The application should return the actual URL to use for the admin panel to reload in the Javascript.