On 6/5/2019 2:40 PM, Gus Heck wrote:
Experiences that force the user to think about the browser cache are
sub-par :). Anything that changes the URL will interrupt caching so just
adding a query parameter &_v=8.1.1 (or whatever) to every request would
probably do the trick, there's no need to mess with file names or file
locations IF the UI can easily do such a thing. One could write javascript
to find all the src/href etc on the page and append... as for whether
that's easy in our actual UI, I don't know. haven't tried to work with it
yet.
I agree, we definitely don't want it to become necessary for the user to
complete a complex action like clearing their cache.
A parameter like what you describe is already on some of the requests
... but not all. Here are two requests that I see from the browser:
http://localhost:8983/solr/css/angular/segments.css?_=8.1.0
http://localhost:8983/solr/libs/angular.js
So if we can figure out how to get that parameter applied to more
requests, it would hopefully solve this.
Thanks,
Shawn
