Skip to content
This repository has been archived by the owner on May 1, 2023. It is now read-only.

Handle expired s3 content on website #68

Open
dj2 opened this issue Aug 13, 2021 · 2 comments
Open

Handle expired s3 content on website #68

dj2 opened this issue Aug 13, 2021 · 2 comments

Comments

@dj2
Copy link
Contributor

dj2 commented Aug 13, 2021

We expire reports and screenshots from the s3 buckets after 30 days. We should make sure that anywhere we show links to this content (or for screenshots the content itself) we check the creation date and so an expiry message if the 30 day window has expired instead of non-functional links/images.

@maxneuvians
Copy link
Contributor

We should have the id creation time in the DB and the API could return a 410 or something like that if the timestamp > 30 days

@dj2
Copy link
Contributor Author

dj2 commented Aug 13, 2021

Maybe for images we have a generic expired image we return. For reports, it would be preferable if we just didnt' show the link at all.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants