Project

General

Profile

Actions
Copy link

Bug #40754

open

mgr/dashboard: configure HTTP caching for static files (JS/Angular)

Added by Ernesto Puerta almost 5 years ago. Updated about 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
General
Target version:
Ceph - v14.2.1
% Done:

0%

Source:
Community (dev)
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

A Rook issue might be (still under investigation) caused by a long-term caching of JS assets (dashboard Angular front-end) causing an older version of the front-end to interact with a newer Python back-end. Regardless any discussions on backward compatibility, this behaviour should be reviewed. According to RFC7234, in the absence of cache control headers, it should be assumed that web browsers and HTTP proxies can unconditionally cache contents. Last-Modified headers (added by default by CherryPy) should result in some cache revalidation (10%) but it seems that's not enough.

Hence the recommendation is to set Cache-Control headers. Let's use this issue to experiment and discuss the specific settings:
- no-cache would trigger cache revalidation for every request, so perhaps having a small max-age could work better.

Actions
Copy link

Also available in: Atom PDF