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
{{ message }}
This repository has been archived by the owner on Jun 10, 2024. It is now read-only.
I'm using S3 for file storage through the boto3 storage class. When generating links to files signatures are created to authorise access to files and these include an expiry.
At the moment when files are submitted through a form the value stored for the file includes all the additional params required. This includes the signature and expiry so the default expiry time of 1 hour, for example, means a submission can only be viewed for an hour.
Really the path to the file should be stored, then when the submission is viewed in admin, the URL should be pulled from the storage class so that it can set a signature at that point, allowing for 1 hours viewing from the point the submission is opened in admin.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm using S3 for file storage through the boto3 storage class. When generating links to files signatures are created to authorise access to files and these include an expiry.
At the moment when files are submitted through a form the value stored for the file includes all the additional params required. This includes the signature and expiry so the default expiry time of 1 hour, for example, means a submission can only be viewed for an hour.
Really the path to the file should be stored, then when the submission is viewed in admin, the URL should be pulled from the storage class so that it can set a signature at that point, allowing for 1 hours viewing from the point the submission is opened in admin.
The text was updated successfully, but these errors were encountered: