Title
Date: 2024-11-14
Status: accepted
Scope
- [x] backend
- [x] mtam-components
Context
To increase the performance of pages that use our mtam/init.js endpoint, we want to allow caching. On the other hand, we need to ensure that the client receives a new version with new features or fixes when required so that no problems with caching occur.
Decision
We have decided that we only cache client wise, not in the whole CDN, since the content is user specific (private). A response is instantly stale; a client checks if there is a new version available via a ETag with which it can determine whether the file has changed.
Consequences
There will be a request to mtam/init.js on every reload.