Closed t83714 closed 10 months ago
Our gateway will, by default, cache most responses unless the frontend explicitly requests to turn it off:
https://github.com/magda-io/magda/blob/master/deploy/helm/internal-charts/gateway/values.yaml#L200
For performance consideration, we cache most of the dataset pages by default.
As the user's visibility might change while the role changes, the cache could sometimes create confusion.
Although the user can turn off the gateway cache at deployment time via helm chart config, it would be better if we could:
no-cache
closed via PR: https://github.com/magda-io/magda/pull/3489
Better Handling Dataset Page Cache At Frontend
Our gateway will, by default, cache most responses unless the frontend explicitly requests to turn it off:
https://github.com/magda-io/magda/blob/master/deploy/helm/internal-charts/gateway/values.yaml#L200
For performance consideration, we cache most of the dataset pages by default.
As the user's visibility might change while the role changes, the cache could sometimes create confusion.
Although the user can turn off the gateway cache at deployment time via helm chart config, it would be better if we could:
no-cache
responses for non-anonymous users