-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🚀 Feature: Configure Client-Side Cache Control For Storage #7281
Labels
backlog
Issues waiting in the backlog
product / storage
Fixes and upgrades for the Appwrite Storage.
Comments
Is this up for grabs? Would love to pick it up and implement a solution. |
Is this issue still up for grabs and can be assigned to me? |
@stnguyen90 Is this issue still up for grabs? |
@golu360, thanks for your interest! Unfortunately not. This one would require internal discussion and our design team to be involved. For now, if you're interested in this feature, make sure to add a 👍🏼 . |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backlog
Issues waiting in the backlog
product / storage
Fixes and upgrades for the Appwrite Storage.
🔖 Feature description
Cache headers (ETag, Max-Age,..) should be configurable for files in Storage. This can be done in the following ways:
ETag may be selectable as static value, hash or date.
🎤 Pitch
Depending on usage of files stored in the Storage, files may have different caching requirements for optimal user experience. A customer should be able to tune caching to their needs with global defaults and fine-grained control.
For example, an avatar image may be cached for hours to days, while diagrams may need to be refreshed more frequently. Logos or documents may even be cached for weeks!
Allowing control over the headers is a simple and efficient way to enable this feature while not costing any additional resources.
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: