UI: UI application cached after upgrade
Bug #1883232 reported by
Alberto Donato
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Undecided
|
Unassigned | ||
| maas-ui |
Fix Released
|
Unknown
|
|||
Bug Description
After a maas snap upgrade (on bolla.internal) which brought the UI from v1.3.1 to v1.3.2, loading the UI in a chromium browser session where I've previously used MAAS still loaded the 1.3.1 UI.
It seems there's a very aggressive caching. Loading the UI in a private session got me the new UI, but the already existing session seems to never reload the UI even with a force refresh.
Selecting "disable cache" in the inspector eventually caused a full refresh which got me 1.3.2.
I'm not entirely sure if this is a js issue or might be related to the server returning a wrong Last-Changed date for /r/index.html, which causes the browser not to load the correct js file.
| Changed in maas-ui: | |
| importance: | Undecided → Unknown |
| summary: |
- UI application cached after upgrade + UI: UI application cached after upgrade |
| Changed in maas-ui: | |
| status: | New → Fix Released |
| Changed in maas: | |
| status: | New → Fix Committed |
| Changed in maas: | |
| milestone: | none → 3.3.0 |
| Changed in maas: | |
| milestone: | 3.3.0 → 3.3.0-beta1 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
