[ https://issues.apache.org/jira/browse/GUACAMOLE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daryl Borth updated GUACAMOLE-275: ---------------------------------- Summary: Javascript from older Guacamole extensions is cached browser side (was: Javascript from Guacamole extensions is cached browser side) > Javascript from older Guacamole extensions is cached browser side > ----------------------------------------------------------------- > > Key: GUACAMOLE-275 > URL: https://issues.apache.org/jira/browse/GUACAMOLE-275 > Project: Guacamole > Issue Type: Bug > Components: guacamole-client > Reporter: Daryl Borth > > Guacamole combines the JS from extensions and rolls it into app.js. It then > cache-busts by adding a version string to the app.js (eg: > app.js?v=0.9.12-incubating). > This works great for preventing a browser from serving up JS from older > Guacamole code. But it does nothing to prevent the code from older extensions > from being loaded. We change our extension periodically and there isn't > always a new Guacamole version out. This can lead to backwards-incompatible > changes breaking the application. > Can some sort of cache busting or expiration of some sort be added? > Preferably, in the ResourceServlet there'd be some new headers added, eg: > Cache-Control: no-cache or at least an Expires header -- This message was sent by Atlassian JIRA (v6.3.15#6346)