-
Notifications
You must be signed in to change notification settings - Fork 8.5k
Prevent caching for dynamic content #8530
Copy link
Copy link
Closed
Labels
Team:CorePlatform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t//Platform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t//enhancementNew value added to drive a business resultNew value added to drive a business result
Metadata
Metadata
Assignees
Labels
Team:CorePlatform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t//Platform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t//enhancementNew value added to drive a business resultNew value added to drive a business result
Type
Fields
Give feedbackNo fields configured for issues without a type.
We currently send E-Tags to ensure that caches are correctly invalidated, but as more people put more sensitive data in Elasticsearch and view it in Kibana, is this still okay? In order to make use of E-Tags browsers must store the response somewhere, which means that sensitive data _could_ be leaked (in extraordinary circumstances).
Adding the
Cache-control: no-storeandPragma: no-cacheheaders will prevent the browser from caching these responses.