-
Notifications
You must be signed in to change notification settings - Fork 8.6k
Update our Cache-Control header #58169
Copy link
Copy link
Closed
Labels
Feature:HardeningHarding of Kibana from a security perspectiveHarding of Kibana from a security perspectiveTeam:SecurityPlatform Security: Auth, Users, Roles, Spaces, Audit Logging, etc t//Platform Security: Auth, Users, Roles, Spaces, Audit Logging, etc t//
Metadata
Metadata
Assignees
Labels
Feature:HardeningHarding of Kibana from a security perspectiveHarding of Kibana from a security perspectiveTeam:SecurityPlatform Security: Auth, Users, Roles, Spaces, Audit Logging, etc t//Platform Security: Auth, Users, Roles, Spaces, Audit Logging, etc t//
Type
Fields
Give feedbackNo fields configured for issues without a type.
Today we set the Cache-Control header to no-cache. The current best practice advice we're seeing states
This is not a security vulnerability to be missing these headers, it is a security hardening measure