Properly invalidate browser caches after updates
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.
Add random seed to signin URL before going from reboot to signin page to force browser reload
- 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.