Zammad used to have some custom HTTP cache handling code, which turned out to be obsolete and thus removed for better maintainability.
- `Pragma` is deprecated and not recommended to be used any more
- `Expires` is not really needed, if `Cache-Control` sets a `max-age`
- `Cache-control`: `no-store` includes `no-cache`. Other directives like `max-age` and `must-revalidate` are irrelevant in this case.
The Rails default response header of `max-age=0, private, must-revalidate` should be perfect to enforce requests to always be sent to the server, rather than served from the cache.
See also
- https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control
- https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Expires
- https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Pragma
- Translations are no longer fetched from the cloud.
- Instead, they are extracted from the codebase and stored in i18n/zammad.pot.
- Translations will be managed via a public Weblate instance soon.
- The translated .po files are fed to the database as before.
- It is now possible to change "translation" strings for en-us locally via the admin GUI.
- It is no longer possible to submit local changes.
