-
Notifications
You must be signed in to change notification settings - Fork 8.5k
Allow browsers to cache static assets #6520
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 resultgood first issuelow hanging fruitlow hanging fruit
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 resultgood first issuelow hanging fruitlow hanging fruit
Type
Fields
Give feedbackNo fields configured for issues without a type.
Right now we send
cache-control: no-cachein response to requests for the webpack generated css and js bundles, and probably other static assets. Since these files only change as often as the Kibana version, and we already send the build number as a query param in the request to bust the cache, we should totally allow the browser to cache them. But Kibana is a single page app you say, it's only the initial page load that's slow so it's not that important. But that's not always the case.