How does url parameter "noexpires" work? And how can I check that?
I've put "noexpires" into an aXes project url like /ts/ts2/index.html?noexpires&...... and have checked how it works by using F12 developer tool of IE11.
In my understanding, screen files (screen_xxx.js) are loaded from server without clear the cache. Is that correct?
From my quick test, however, they seemed to be loaded from the cache when the 2nd or following access.
Yes this is correct. This "forces" the browser to reload all files loaded by aXes.In my understanding, screen files (screen_xxx.js) are loaded from server without clear the cache. Is that correct?
Most of the time, you need to close and launch the browser again for this to work. It is the same when clearing the cache, sometimes you need to close and launch the browser after clearing cache between the 1st time and the second time, and between the second and the third time....From my quick test, however, they seemed to be loaded from the cache when the 2nd or following access.
Thanks for the comment. I understand what you are saying. But there is something that I want to confirm.
In my further testing, I found this (using F12 of IE11):
- In development mode, "noexpires" looks like it is working as expected.
---> screen_xxx.js was always loaded from the server.
- In user mode, it looks like it is NOT working as expected.
---> screen_xxx.js was loaded from the cache in the 2nd or following access.
When you have time, could you double-check on that please? (There is no rush.)
(Why I posted this, because one customer has been refusing changing their internet options of IE11. So if "noexpires" works well, it would be nice.)