Skip to content

Prevent caching for dynamic content #8530

@spalger

Description

@spalger

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-store and Pragma: no-cache headers will prevent the browser from caching these responses.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Team:CorePlatform Core services: plugins, logging, config, saved objects, http, ES client, i18n, etc t//enhancementNew value added to drive a business result

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions