Project

General

Profile

Bug #59904

Properly invalidate browser caches after updates

Added by Eric Loewenthal about 2 months ago. Updated 5 days ago.

Status:
In Progress
Priority:
No priority
Assignee:
Damian Szidiropulosz
Category:
GUI (new)
Target version:
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

There's a fairly steady trickle of reports from the forums (and my personal experience) that the new GUI ends up not working after an update, because it was using some stuff from the browser cache instead of downloading the new version from the server.

This behavior is particularly nasty because the GUI generally looks correct. Symptoms typically involve non-functional UI elements like buttons, so users tend to flail around a bit (I speak from experience) until they either figure it out on their own or are told to clear the browser cache.


Related issues

Has duplicate FreeNAS - Bug #59886: Gui unavailable after upgrade - required browser clean to enable GUI againClosed

Associated revisions

Revision 98d5cd89 (diff)
Added by Erin Clark about 1 month ago

Add random seed to signin URL before going from reboot to signin page to force browser reload

Ticket: #59904

Revision a4d86118 (diff)
Added by Erin Clark about 1 month ago

Add random seed to signin URL before going from reboot to signin page to force browser reload

Ticket: #59904
(cherry picked from commit 98d5cd8938c7533f6d0c46c5c4fb48fb8b89761d)

History

#1 Updated by Dru Lavigne about 2 months ago

  • Has duplicate Bug #59886: Gui unavailable after upgrade - required browser clean to enable GUI again added

#2 Updated by Erin Clark about 1 month ago

  • Assignee changed from Release Council to Erin Clark

What browser are you on?

#3 Updated by Dru Lavigne about 1 month ago

  • Status changed from Unscreened to In Progress
  • Target version changed from Backlog to 11.2-U2

#4 Updated by Erin Clark 7 days ago

  • Assignee changed from Erin Clark to Damian Szidiropulosz

Damian had a better solution to this problem, passing to him

#5 Updated by Erin Clark 5 days ago

  • Target version changed from 11.2-U2 to 11.2-U3

We have some ideas on how to do this, either have a datestamp or some kind of incrementing file somewhere in the repo that tells the browser that the UI has been updated however hashing out the implementation details and testing this will take quite a bit of time, given how close this is to code freeze we are going to push this to U3 so we can make sure we do this right the first time.

Also available in: Atom PDF